Query work items using WIQL or predefined queries
AI agents call query_work_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 retrieves and queries work items without creating, modifying, or deleting data. It is a Read operation. Severity is medium because work items may contain sensitive project information, schedule details, or business logic that could be misused if an AI agent exfiltrates large volumes or queries unauthorized items, but the tool itself has no destructive capability.
From the tool's definition Tool name 'query_work_items' and description 'Query work items using WIQL or predefined queries' indicate data retrieval operations. WIQL (Work Item Query Language) is a query language for retrieving work item data from Azure DevOps without modification.
Attacks that exploit this kind of access
Query work items using WIQL or predefined queries. 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 query_work_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.
query_work_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 query_work_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 query_work_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.
query_work_items is provided by the Azure DevOps MCP Server MCP server (jaybird-us/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 →