Guardrails that assume the AI can be tricked
Every AI system that processes natural language is susceptible to prompt injection. Lorikeet is designed so the things that matter most don’t depend on the AI being unbreakable.
Deterministic boundaries. AI-layer checks.
Tier one
Hard boundaries no prompt can cross
Customer isolation, server-side identity validation, workflow-scoped tool access and hard execution caps are enforced in code rather than prompts, so a manipulated conversation cannot reach beyond its own blast radius.
Tier two
Checks on messages coming in and going out
Incoming messages pass a prompt-injection classifier and bad-actor checks, while response guardrails screen what the agent says for grounding and policy, with the ability to block, rewrite or escalate. Deterministic string-matching rules catch the phrases you never want sent.
Escalation
Guardrail events are tracked, not hidden
When a guardrail fires, the conversation can escalate to your team with full context, and every event lands in your analytics as a tracked outcome your QA team can review.
Designed for blast radius, not immunity claims
We don’t claim the AI is unbreakable. Any vendor claiming immunity to prompt injection is either uninformed or dishonest. Lorikeet’s design goal is that the blast radius of any successful manipulation is a single conversation: no lateral movement, no persistent compromise, and nothing the agent can do that its deterministic boundaries don’t allow.
Frequently asked questions
What are AI guardrails in customer support?
Guardrails are controls that keep an AI support agent inside the boundaries you set. In Lorikeet they come in two tiers: deterministic boundaries enforced in code, such as scoped tool access and execution caps, and AI-layer checks that screen incoming messages and outgoing responses for injection attempts, grounding and policy.
Can prompt injection be prevented entirely?
No, and vendors who claim otherwise should worry you. Every system that processes natural language can be manipulated. The design question is what happens when it is: Lorikeet limits the blast radius to a single conversation, with no lateral movement and nothing outside the agent’s deterministic boundaries.
What happens when a guardrail fires?
Depending on your configuration, the response can be blocked, rewritten or escalated to your team with full conversation context. Every guardrail event is also recorded as a tracked outcome in your analytics, so QA teams can review exactly what fired and why.
How do guardrails reduce hallucinations?
Grounding checks compare what the agent wants to say against your knowledge sources and flag unsupported claims, and the agent escalates when it lacks the information to answer. Reduction is the honest promise: Coach then scores conversations in production so anything that slips through gets caught and fixed.
Are guardrails configurable?
Yes. You can write custom guardrail rules in plain language, add deterministic string-matching rules for phrases that must never be sent, and test all of it pre-launch with guardrail test scenarios run as simulations.
