PolicyLayer | Never answer your agent twice

# PolicyLayer > PolicyLayer is the hosted control plane for production MCP. It enforces customer-defined rules on every MCP tool call — allow, deny, rate-limit, or require human approval — before agents can touch payments, infrastructure, code, data, or customer operations. Customers define the rules. PolicyLayer enforces them at the execution boundary. > Agent View: a clean markdown overview of the whole site lives at https://policylayer.com/index.md. Most pages also serve a markdown mirror — append .md to any /docs/, /blog/, /attacks/, or /glossary/ URL, to the key product pages (/mcp-gateway.md, /mcp-security.md, /pricing.md, /registry.md, /agents.md), and to every registry record page: /tools/<server>.md for a server's full record (identity, posture, grade, all tools classified) and /tools/<server>/<tool>.md for a single tool (parameters, example tools/call request, install command, risk analysis, recommended policy). For the full text of the site's content (manifesto, blog posts, attack database, MCP incidents, research, glossary) in one bounded file, see: https://policylayer.com/llms-full.txt. ## MCP Registry — the data product One continuously verified record per MCP server: 30,000+ servers, 500,000+ tool versions tracked. Each record carries identity confidence (verified / unverified / mismatch, evidence published), probed auth posture, an A–F risk grade, and the full tool surface classified per tool (category, risk weight, capability flags, OWASP classes, suggested policy default). Records follow ecosystem changes within the hour. - [Registry search](https://policylayer.com/registry) — look up any server; every published server also has a record page at /tools/<slug> - [Registry API](https://policylayer.com/registry/api) — free /v0 endpoint in the official MCP Registry shape; licensed /v1 feed with full records, ordered change feed, signed webhooks, nightly snapshot - [Registry licence](https://policylayer.com/registry/pricing) — $199/m