49 tools. 29 can modify or destroy data without limits.
29 write tools that can modify data. Rate limits recommended.
Last updated:
Write operations (appconfig, appservice, communication) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
Execute tools (deploy, loadtesting) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
Intercept sits between your agent and Azure. Every tool call checked against your policy before it executes — so your agent can do its job without breaking things.
npx -y @policylayer/intercept scan -- npx -y @Azure/azure-mcp appconfig:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
acr:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
The Azure server has 27 write tools including appconfig, appservice, communication. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.
49 tools across 3 categories: Execute, Read, Write. 20 are read-only. 29 can modify, create, or delete data.
One line change. Instead of running the Azure server directly, prefix it with Intercept: intercept -c azure.yaml -- npx -y @@Azure/azure-mcp. Download a pre-built policy from policylayer.com/policies/azure and adjust the limits to match your use case.
Starter policies available for each. Same risk classification, same one-command setup.
Set budgets, approvals, and hard limits across MCP servers.
npx -y @policylayer/intercept init