Lakera Guard
Lakera Guard screens AI application interactions for security and safety risks and provides Enterprise APIs for managing guardrail policies and projects.
Integration
- Vendor
- Lakera Guard
- Category
- other
- Auth
- API_KEY
- Tools
- 10
- Composio slug
lakera_guard
Tools
- 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, updates, and deletion re
- Delete Policydestructive
Permanently delete an Enterprise Lakera policy by ID. The provider rejects deletion while any project is assigned to the policy.
- Delete Projectdestructive
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.
Setup
- Create or open a Switchy Project.
- Open Integrations and connect Lakera Guard.
- Authorise through api_key. Switchy stores the connection against your org.
- Everyone in the Project can now @-mention the Lakera Guard tools in chat.
What teammates see: by default, memories from Lakera Guard are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.