42 tools. 6 can modify or destroy data without limits.
6 write tools that can modify data. Rate limits recommended.
Last updated:
Community server · catalogue entry verified 02/07/2026
Running more than one server? Check your whole stack →
6 of Google's 42 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 Google, and nothing reaches the server without passing your rules. These are the rules we recommend:
{
"ado_create_work_item": {
"limits": [
{
"counter": "ado_create_work_item_per_hour",
"window": "hour",
"max": 30,
"scope": "grant"
}
]
}
} Prevents bulk unintended modifications from agents caught in loops.
{
"ado_get_backlog": {
"limits": [
{
"counter": "ado_get_backlog_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.
The Google server has 4 write tools including ado_create_work_item, ado_mark_done, ado_update_work_item. 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 Google.
42 tools across 2 categories: Read, Write. 36 are read-only. 6 can modify, create, or delete data.
Register the Google 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 42 Google tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Instant setup, no code required.
42 Google tools catalogued and risk-classified — across an index of 43,000+ MCP servers.