AI_risk_compliance/rules
Let agents work.
Know their limits.
A local checkpoint for every command. A shared record for every decision. Give your AI agents room to work, with boundaries your team can see.
Open-source AgentShield · Local evaluation · Your existing agents
Select a module to look inside
git statusALLOWRead-only command. Safe work continues; the decision is recorded.
No model calls.
Shell commands and MCP tools.
Coverage grows every day.
Live counts from the rule corpora behind AgentShield and Comply, recorded daily.
AI_risk_compliance/taxonomy
AI_Agent_Shield/packs
Look inside.
One layer at a time.
Scroll through compliance, audit evidence, AgentShield and your agents. Each layer reveals the part it plays in the system.
A request enters through an agent hook or MCP proxy. Select a module in the illustration to look inside.
SCROLL TO THE NEXT LAYER
Turn activity into evidence.
Connect runtime decisions to compliance controls. See which controls real activity exercises, then export the record for your security team and auditor.
Mappings support a review. They do not replace certification or an audit.
Every decision has a story.
Bring decisions together across your fleet. See the command, the matching rule, and the reason in one hash-chained audit trail. Follow an action from its source to its outcome.
Each event links to the previous record, making changes detectable.
A boundary before execution.
Local rules evaluate each action before it runs. Allow safe work, record what needs review, and block actions that cross your policy. Start in audit-only mode to see the impact first.
git statuscat ~/.ssh/id_rsaIllustrative enforcement decisions. Switch policy mode in the explorer above to compare.
Your agents get to work.
A shell command. A file read. An MCP tool call. AgentShield sits at the point where intent becomes action, alongside the tools your team already uses.
git statusThe command is evaluated before execution.
Every action. In view.
Example activity| Command | Agent | Decision |
|---|---|---|
git status |
Claude Code | Allowed |
cat ~/.ssh/id_rsa |
Cursor | Blocked |
chmod -R 777 /var/www |
Claude Code | Audited |
Try a command.
See the reasoning.
Paste a shell command or choose an example. AgentShield checks it against the community rules and explains its decision. No commands are executed.
Your fleet. One clear record.
- Fleet. Every agent, its rules, its last check-in.
- Policy. Enable a framework; rules reach every machine.
- Audit trail. Hash-chained, exportable.
- Posture. Which controls real activity exercises.
| Rule | Decision | Fires | Control |
|---|---|---|---|
| sec-block-git-log-credential-mining | BLOCK | 59 | CC6.1 · CC6.7 |
| ai-mcp-tool-description-poisoning | BLOCK | 51 | CC6.8 · CC7.2 |
| sec-df-block-cred-to-network | BLOCK | 40 | CC6.7 |
| ai-llm-output-code-eval-python | AUDIT | 52 | CC7.2 · CC8.1 |
| ne-block-dns-exfil-backtick | BLOCK | 21 | CC6.7 |
Powerful agents need boundaries.
Agents inherit your permissions. Their actions deserve the same visibility and controls as the rest of your stack.
No exploit required
One poisoned tool description or README is enough to send a private key to a stranger. How →
Check the action itself
EDR sees a trusted shell. The firewall sees HTTPS. AgentShield checks the command before it becomes an action.
A record you can stand behind
"How do you control what your AI agents can do? Show me the record." Most teams can't. What that looks like →
Install once.
Work with confidence.
Four commands on a laptop, one switch in the dashboard.
Read the setup guide →Install AgentShield
One Homebrew command. Prebuilt binary, macOS and Linux.
Hook your agent
Claude Code, Cursor, Windsurf, Codex CLI, Gemini CLI, OpenClaw, or the MCP proxy.
Connect your team
Device-code sign-in. Policy and rule packs pull down; decisions stream up.
Watch for a week, then enforce
Read what would have been blocked. Then flip the organisation to enforce.
Clear about what we do.
Checks, without execution.
The agent asks "may I?". We answer.
Evaluation stays local.
No model calls or telemetry in the local evaluator. Connect to Agent Lens when you want a shared audit trail.
Open about its limits.
We publish our own bypasses. Start here →
Start local. Scale with your team.
Start with visibility. Add enforcement and longer retention as your team grows.
Team
- $59/user/month billed annually
- 5-user minimum · model usage paid separately
- Up to 50 members, 100 agents
- Observe, Assist, Limited Autopilot
- OWASP, SOC 2, ISO 27001
- Enforcement, custom rules
- 90-day retention, reports
Enterprise
- Contracted team and fleet capacity
- Adds GDPR and HIPAA
- Custom data labels
- 1-year retention, priority support
Your next agent.
With a clear boundary.
Install on your own machine first. Then invite the team. [email protected]