SHRIKEMCP gateway
An MCP gateway is a security proxy between AI agents and the MCP servers they use. Tool listings and calls pass through it, where definitions are screened, calls are checked against policy before executing, outputs are scanned, and every decision is logged. One enforcement point governs every server behind it.
The gateway pattern exists because per-server, per-agent controls stop scaling early. Placing governance in the traffic path means enforcement does not depend on the agent cooperating, and gives the security team a single place to set policy and read evidence. The full treatment, including how a gateway differs from an MCP server and an API gateway, is at What is an MCP gateway?
Related
Shrike governs AI agent actions in real time: every command, query, and tool call evaluated against policy before it executes. Start with what is action governance or the quickstart.