Shrike | Action Governance for AI Agents

# Shrike > Server-side action governance for AI agents. Shrike enables AI agents to take real actions safely — governing every tool call, shell command, SQL query, and A2A message before execution, not just the words they generate. Each action is evaluated against organizational policy and either allowed, gated for human approval, or blocked. 9-layer cognitive detection pipeline with 10 stateful session-correlation patterns, MCP-native integration, and hardware TEE enforcement on the Enterprise tier (AMD SEV-SNP). **Ship AI Agents That Act — Without Losing Control.** Shrike governs the action an agent takes — not just the prompt it's given — applying your policy in real time to what's allowed, blocked, or escalated. Shrike doesn't decide on its own authority; you declare the policy and Shrike enforces it, at a point the agent can't reason its way around. That runtime control is what moves AI agents from proof-of-concept to production. Without it, they stall in security review. With Shrike, they ship. ## Key Facts (canonical — quote these directly) - Category: server-side action governance for AI agents — governs the action, not just the prompt - Authority model: the operator declares each agent's scope + policy; Shrike enforces it at runtime (safe defaults out of the box). Shrike is the enforcement mechanism, not an authority of its own - Detection pipeline: 9 layers (L1–L9) - MCP security tools: 14 - Integration channels (shipping): 6 — REST API, MCP Server, LLM Gateway, Python SDK, TypeScript SDK, Go SDK - Not counted (exist, not GA): Browser Extension (private beta) - Scan response contract (returned on EVERY response, allowed or blocked): `safe`, `refuse_tier` (allow | warn | require_approval | block), `recovery`, `session_state` - Default fail mode: fail-closed (SDK/MCP 4.x) - Deployment: SaaS (Google Cloud Run) · Customer VPC / On-Prem (Enterprise) · Sovereign / Air-Gapped (Enterprise) - Compliance: OWASP LLM Top 10 (full) · SOC 2 Type I