Straza governs what your AI agents do.

Your identity governance system decides who. Straza enforces what their agents may do, at every action.

  1. Identity

    Your IGA sends your people, your AI agents and a sponsor for each agent: the person accountable for it.

  2. RBAC

    You make roles from the tools of MCP servers. Nothing is reachable until a role says so.

  3. MCP gateway

    Your MCP servers sit behind one gateway. An MCP server offers tools to an agent, such as restarting a service.

  4. Delegated MCP administration

    Every MCP server gets its own admin role. The team that owns a server runs it and no other, and your IGA decides who gets the role.

  5. Human in the loop

    Fine-grained approvals for MCP tools and shell commands. You choose which calls need a person’s yes. No answer is a deny.

  6. Policy

    Every tool call is decided before it runs. It is allowed, denied, or it waits for a person.

  7. Credentials

    The gateway adds a server’s credential after the decision, so the agent never has it.

  8. Audit

    Every decision, allowed or denied, goes into a hash chain, and a sink copies it to your SIEM.

On this page6 sections

One path from every agent to every tool

Every agent action passes through Straza. Identity comes in from your IGA, and the audit chain streams out to your SIEM.

Agents

  • Claude Code
  • Codex
  • Gemini CLI
  • Python agents
  • Any other LLM
  1. 01 Identity
  2. 02 RBAC
  3. 03 Policy
  4. 04 MCP gateway
  5. 05 Human in the loop
  6. 06 Credentials
  7. 07 Audit

your IGA

SCIM 2.0 or REST

Audit sinks

file

webhook

your SIEM

MCP servers

  • billing
  • deployer
  • helpdesk
  • crm
  • + any MCP server
Roles outRBACtoyour IGA
Identity inyour IGASCIM 2.0 or REST
Audit outwebhookfiletoyour SIEM
FIG 1 · Agents are hooked, or restricted so that straza exec is the only shell they get.

Your IGA grants the roles that expose tools.

You create roles in Straza and bind tools to them. Your IGA imports the roles and decides who gets each one.

FIG 2 · A role made in Straza from three of a server's eight tools is imported by your IGA and assigned to the agent, the running session gets those tools, and Straza decides each call and records it. With midPoint as the IGA, the import takes about ten seconds, and the running session takes the assignment at its next check-in.

Approvals are signed on the device

Every decision on the phone is signed by a hardware key that is generated there and never leaves it. If the phone is lost, an administrator revokes it server-side, its token stops working, and the pairing is gone.

On iPhone and Android today. The console, a browser page and Slack are approver channels alongside the phone.

FIG 3 · Human in the loop. An agent is asked to restart checkout on prod, the call waits, a person approves on the phone, the service restarts.
What the video shows, step by step
  1. joe-java-developer-agent is asked in a terminal to restart the checkout service on prod with deployer.
  2. Straza stops the call before it runs, and the agent waits for a person.
  3. The approver app lists restart service in deployer. The approver reads the tool, the requester and the exact arguments, taps Approve and enters the device PIN.
  4. The app shows "Recorded: approved" and the agent reports the checkout service restarted and healthy.

One MCP gateway, one policy, one audit chain

RBAC for every tool. Nothing is reachable until a role says so.

FIG 4 · A public MCP server goes live in Straza and nobody can call it. A role then allows one of its tools and makes a second one need approval, and an agent whose business role includes that role lists the two tools and runs a search.
What the video shows, step by step
  1. The console's MCP servers page reads "0 servers". A person clicks Add MCP server, types the address https://learn.microsoft.com/api/mcp and changes the suggested name learn to microsoft-learn.
  2. The credential step stays on None. The review reads "Nobody can call it until a role gives access to its tools." The person clicks Save and publish and confirms in "Publish microsoft-learn?".
  3. The console reports "microsoft-learn is live. Straza reached it and read 3 tools."
  4. Give access to it opens a new role, which the person names microsoft-learn-docs. Under Choose per tool the person ticks microsoft_docs_search and microsoft_docs_fetch. The third tool, microsoft_code_sample_search, stays unticked and reads "no access".
  5. The person sets microsoft_docs_fetch to Needs approval, decided by "The agent's sponsor" through "A ticket, granted within" one day, then one hour to run. The summary reads "1 tool is allowed. 1 needs a ticket the agent's sponsor grants within a day, after which the same call is allowed for an hour." The role is published and the console reports "microsoft-learn-docs is live."
  6. On the business role java-developer the person clicks Compose a role, picks microsoft-learn-docs, types the role's name to confirm and publishes. The role's page then lists microsoft-learn with "2 tools via microsoft-learn-docs".
  7. In the agent's terminal, joe-java-developer-agent is asked "Which microsoft-learn tools can you call? Then search the docs for Java on Azure Container Apps, one line." It lists microsoft_docs_search and microsoft_docs_fetch, runs the search and answers with a link to Microsoft Learn. The status line reads "2 roles" and "2 MCP tools".
Fail-closed
Platform unreachable: an approval-gated call denies within two seconds.
Self-hosted
One server binary, laptop to Kubernetes. No callout to us at decision time.
Open source
Core AGPL-3.0-only. SDKs, spec, plugins and the approver app Apache-2.0.
No AI inside
Enforcement is deterministic policy evaluation.
Agents can draft
With the drafting role, an agent proposes a change to servers, roles or policy. Straza checks it, and only a person publishes it.

Releases

  1. v2.2.0

    An AI agent can call an MCP server as its own Microsoft Entra agent identity. The console writes rules for MCP servers on people's own machines.

  2. v2.1.0

    A tool that tells an agent what it may do. Pin a server's objects in the console.

  3. v2.0.0

    Every credential on a person's machine moves into a local service that agents running as that person cannot read. Roles that cover some objects of a server, git through Straza, rules by tool name.

Full changelog · How Straza compares with five other open-source projects

Run it yourself

The whole stack on one machine

Straza with midPoint as the IGA, Keycloak and a working AI agent. Needs Docker with Compose 2.24 or later, 4 cores, 8 GB of memory and 20 GB of disk. Run it on a trusted network only.

Demo stack
git clone https://github.com/strazahq/straza.git && cd straza
deploy/compose/eval-stack/up.sh
docker compose -p straza-eval logs -f --no-log-prefix eval-seed

Standalone

No Docker. Get strazad and straza from the releases page and follow the guide. It starts the server, enrolls your machine and connects Claude Code. A starter rule denies rm -rf, and a rule you add makes git push wait for your approval in the browser.

Try it on one laptop

Or hand it to your coding agent

Prompt
Read https://straza.ai/llms.txt and https://docs.straza.ai/evaluate/try-it-on-one-laptop/. Then set up Straza on this machine in standalone mode, enroll it, and show me one command that policy denies.