Connect Lakera Guard to your AI agent
Lakera Guard screens AI application interactions for security and safety risks and provides Enterprise APIs for managing guardrail policies and projects.
We set up the connection using your own Lakera Guard account, with keys you control, and keep it running. Your agent picks it up and starts doing the work.
What your agent can do in Lakera Guard
Each one is a real action the agent can take on its own, the same things a person clicking around Lakera Guard could do. Read-only by default; write actions are confirmed against your policy.
- Create Policy Create an Enterprise Lakera policy with built-in detectors and/or custom guardrails. Lakera may omit the new policy ID; if omitted, later retrieval, replacement, and deletion require external policy lookup.
- Create Project Create an Enterprise Lakera project, optionally assigning a policy, metadata, and detect-or-flag action. Omit policy_id to use the default policy. Lakera does not return the generated project ID, so later retrieval, upd…
- Delete Policy Permanently delete an Enterprise Lakera policy by ID. The provider rejects deletion while any project is assigned to the policy.
- Delete Project Permanently and irreversibly delete an Enterprise Lakera project by ID. Historical requests lose their association with the project's metadata and assigned policy.
- Evaluate Detectors Evaluate content and return one confidence result per configured detector without producing an aggregate flagging decision or Guard screening log. Use for analysis and tuning, not runtime allow/block decisions.
- Get Policy Retrieve an Enterprise Lakera policy by ID, including its detector configuration, custom guardrails, version, and assigned projects.
- Get Project Retrieve an Enterprise Lakera project by ID, including its assigned policy, metadata, and detect-or-flag action.
- Screen Content Screen the latest LLM or agent interaction with Lakera Guard and return the policy decision. Use this for runtime allow/block decisions; earlier messages provide context, but only the latest interaction is screened.
- Update Policy Replace an Enterprise Lakera policy's complete configuration and create a new policy version. Omitted detectors or custom guardrails are removed, so retrieve the policy first when preserving existing settings.
- Update Project Update an Enterprise Lakera project by ID. Name is required by the official request schema; retrieve the project first when preserving its current name or other optional settings.
How we connect it
- 1
Connect your account
You create a key in Lakera Guard, a key you create and control, and paste it in once. It lives in a secrets store on your server, not with us.
- 2
Set the guardrails
Read-only by default. You choose which write actions the agent may take, and anything outside that policy gets confirmed with you first.
- 3
We keep it running
Health checks on every connection, updates handled for you, and we watch the first week of activity to make sure the work lands.
FAQ
Lakera Guard questions, answered.
Ready to put Lakera Guard to work?
Tell us what your team runs on. We set up the connection, secure it, and your agent takes it from there.
All product names, logos, and brands are property of their respective owners; used for identification only. ZeroToClaw is not affiliated with or endorsed by Lakera Guard.