39 tools. 19 can modify or destroy data without limits.
3 destructive tools with no built-in limits. Policy required.
Last updated:
Community server · catalogue entry verified 03/07/2026
Running more than one server? Check your whole stack →
19 of Mcp Azure's 39 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Azure, and nothing reaches the server without passing your rules. These are the rules we recommend:
{
"ado_delete_attachment": {
"deny_if": [
{
"conditions": [],
"on_deny": "Blocked by default. Requires approval."
}
]
}
} Destructive tools should never be available to autonomous agents without human approval.
{
"ado_add_attachment": {
"limits": [
{
"counter": "ado_add_attachment_per_hour",
"window": "hour",
"max": 30,
"scope": "grant"
}
]
}
} Prevents bulk unintended modifications from agents caught in loops.
{
"ado_abandon_pull_request": {
"limits": [
{
"counter": "ado_abandon_pull_request_per_minute",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
} Controls API costs and prevents retry loops from exhausting upstream rate limits.
Instant setup, no code required.
Other MCP servers with similar tools — same risk classification, starter policies for each.
Yes. The Mcp Azure server exposes 3 destructive tools including ado_delete_attachment, ado_delete_work_item, ado_remove_work_item_link. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.
The Mcp Azure server has 15 write tools including ado_add_attachment, ado_add_comment, ado_add_pull_request_reviewer. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Mcp Azure.
39 tools across 3 categories: Destructive, Read, Write. 20 are read-only. 19 can modify, create, or delete data.
Register the Mcp Azure MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.
Deterministic rules across all 39 Mcp Azure tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Instant setup, no code required.
39 Mcp Azure tools catalogued and risk-classified — across an index of 43,000+ MCP servers.