AI agents call ado_query_sprint to retrieve information from Mcp Azure without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a read-only query operation against Azure DevOps to retrieve sprint-related work item data. It has no side effects, does not modify or delete data, and does not execute code or external operations. The blast radius of misuse is minimal—an agent could retrieve unintended sprint information but cannot cause damage or irreversible changes.
From the tool's definition Tool name and description indicate it 'Consulta' (queries) 'User Stories de un sprint específico' (user stories from a specific sprint) in Azure DevOps. This is a retrieval operation with no modification, deletion, or execution of external commands.
Attacks that exploit this kind of access
Consulta User Stories de un sprint específico en Azure DevOps. It is categorised as a Read tool in the Mcp Azure MCP Server, which means it retrieves data without modifying state.
Register the Mcp Azure MCP server in PolicyLayer and add a rule for ado_query_sprint: 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 Mcp Azure. Nothing to install.
ado_query_sprint 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_query_sprint 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_query_sprint. 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_query_sprint is provided by the Mcp Azure MCP server (soulberto/mcp-azure). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →