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.
Lakera Guard screens AI application interactions for security and safety risks and provides Enterprise APIs for managing guardrail policies and projects.
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 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 require external project lookup.
Permanently delete an Enterprise Lakera policy by ID. The provider rejects deletion while any project is assigned to the policy.
Permanently and irreversibly delete an Enterprise Lakera project by ID. Historical requests lose their association with the project's metadata and assigned policy.
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.
Retrieve an Enterprise Lakera policy by ID, including its detector configuration, custom guardrails, version, and assigned projects.
Retrieve an Enterprise Lakera project by ID, including its assigned policy, metadata, and detect-or-flag action.
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.
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 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.
The Lakera Guard integration connects your Dench AI CRM directly to Lakera Guard, so agents can read and act on your Lakera Guard data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
10 actions are available for agents to invoke on your behalf. Every call runs through Lakera Guard's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Lakera Guard and click Connect — you'll authorize access through Lakera Guard's own sign-in flow. No API keys or code required.
Ask an agent to use Lakera Guard in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Lakera Guard integration connects your AI CRM to Lakera Guard, so AI agents can work with your Lakera Guard data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Lakera Guard integration currently exposes 10 actions, including Create Policy, Create Project, Delete Policy, Delete Project, Evaluate Detectors, and Get Policy. Agents invoke them on your behalf from chat or from automations.
No. You connect Lakera Guard from your Dench workspace using Lakera Guard's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Lakera Guard's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Lakera Guard connection from your workspace settings at any time.