Sanaf AI
Start free
AI Safety Compliance Detection

Lakera Guard, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Lakera Guard account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • AI Safety Compliance Detection
  • Connects with a key
  • 10 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Lakera Guard is

Lakera Guard screens AI application interactions for security and safety risks and provides Enterprise APIs for managing guardrail policies and projects.

You paste in a key from your own Lakera Guard account. It is kept encrypted, and you can withdraw it from inside Lakera Guard whenever you like.

How a run works

One message in, the work done in Lakera Guard.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Lakera Guard. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Lakera Guard account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

10 tools it already has

What it can do in Lakera Guard

These are the ready-made tools your AI employee already has in Lakera Guard. It is not limited to them, but it never has to be taught these.

  • Create PolicyCreate 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 requi
  • Create ProjectCreate an Enterprise Lakera project, optionally assigning a policy, metadata, and detect-or-flag action. Omit policyid to use the default policy. Lakera does not return the generat
  • Delete PolicyPermanently delete an Enterprise Lakera policy by ID. The provider rejects deletion while any project is assigned to the policy.
  • Delete ProjectPermanently and irreversibly delete an Enterprise Lakera project by ID. Historical requests lose their association with the project's metadata and assigned policy.
  • Evaluate DetectorsEvaluate 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
  • Get PolicyRetrieve an Enterprise Lakera policy by ID, including its detector configuration, custom guardrails, version, and assigned projects.
  • Get ProjectRetrieve an Enterprise Lakera project by ID, including its assigned policy, metadata, and detect-or-flag action.
  • Screen ContentScreen 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
  • Update PolicyReplace 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
  • Update ProjectUpdate 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.
Access, and who is in charge of it

You stay the boss of your Lakera Guard account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Lakera Guard account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Lakera Guard is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Lakera Guard and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about Lakera Guard

Can an AI employee really work inside Lakera Guard?
Yes. It signs in to your own Lakera Guard account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Lakera Guard?
No. Nothing moves and nothing is replaced. Your records stay in Lakera Guard, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Lakera Guard account?
You paste in a key from your own Lakera Guard account. It is kept encrypted, and you can withdraw it from inside Lakera Guard whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Lakera Guard?
It has 10 ready-made tools in Lakera Guard today, among them Create Policy, Create Project and Delete Policy. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Lakera Guard and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Lakera Guard and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Lakera Guard?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Lakera Guard is written down with what it did and when.