Get backlog items for a team or project.
AI agents call get_backlog_items to retrieve information from Azure DevOps MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves backlog items, similar to sibling tools like 'get_active_work_items', 'get_closed_work_items', 'get_my_work_items', and 'get_default_backlog', all of which are read-only operations. The blast radius of misuse is minimal—worst case, an agent reads information it shouldn't have access to, but no data is changed or operations executed.
From the tool's definition Tool name 'get_backlog_items' and description 'Get backlog items for a team or project' indicate a retrieval operation with no side effects. No modification, deletion, or execution capabilities are described.
Attacks that exploit this kind of access
Get backlog items for a team or project. It is categorised as a Read tool in the Azure DevOps MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Azure DevOps MCP Server MCP server in PolicyLayer and add a rule for get_backlog_items: 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 Azure DevOps MCP Server. Nothing to install.
get_backlog_items 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 get_backlog_items 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 get_backlog_items. 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.
get_backlog_items is provided by the Azure DevOps MCP Server MCP server (jhlia0/azure-devops-mcp). 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 →