Low Risk

query_work_items

query_work_items

How to control query_work_items ↓

AI agents call query_work_items to retrieve information from MCP Azure DevOps Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

The tool name and context clearly indicate this is a read-only query operation that retrieves work item data from Azure DevOps. No side effects, modifications, or destructive actions are implied. The server description explicitly lists querying work items as a capability distinct from create/update operations (which are listed separately).

From the tool's definition Tool name 'query_work_items' and server description stating 'enabling AI assistants to interact with Azure DevOps services, allowing users to query work items' indicates a querying/retrieval operation.

Documented attack patterns abuse exactly the kind of access query_work_items gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Azure DevOps Server, and nothing reaches the server without passing your rules. This is the rule we recommend for query_work_items:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "query_work_items": {}
  }
}

query_work_items is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register MCP Azure DevOps Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the query_work_items tool do? +

query_work_items. It is categorised as a Read tool in the MCP Azure DevOps Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_work_items? +

Register the MCP Azure DevOps 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 MCP Azure DevOps Server. Nothing to install.

What risk level is query_work_items? +

query_work_items is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit query_work_items? +

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.

How do I block query_work_items completely? +

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.

What MCP server provides query_work_items? +

query_work_items is provided by the MCP Azure DevOps Server MCP server (vortiago/mcp-azure-devops). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Azure DevOps Server tool call.

Deterministic rules across all 21 MCP Azure DevOps Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

21 MCP Azure DevOps Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.