AI agents call ado_get_backlog to retrieve information from Google without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries backlog items from Azure DevOps without performing any side effects. It returns data in a specific order (by stack rank) but does not create, modify, delete, or execute operations. This is a straightforward read operation with minimal risk of unintended consequences.
From the tool's definition Tool name 'ado_get_backlog' and description 'Query Azure DevOps backlog items ordered by stack rank' indicate data retrieval with no modification. The verb 'Query' and the absence of any creation, modification, or deletion language confirm read-only semantics.
Attacks that exploit this kind of access
Query Azure DevOps backlog items ordered by stack rank. It is categorised as a Read tool in the Google MCP Server, which means it retrieves data without modifying state.
Register the Google MCP server in PolicyLayer and add a rule for ado_get_backlog: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Google. Nothing to install.
ado_get_backlog is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ado_get_backlog rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for ado_get_backlog. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
ado_get_backlog is provided by the Google MCP server (psckeithw/mcp-google). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
ado_get_backlog is one line of Google's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →