Low Risk

listWorkItems

List work items based on a WIQL query

How to control listWorkItems ↓

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

Low Risk

This tool queries and retrieves work item data from Azure DevOps using WIQL (Work Item Query Language). It performs a read-only operation with no side effects, no data modification, no code execution, and no destructive actions. The user is fetching existing information, not creating, modifying, or deleting data.

From the tool's definition Tool name 'listWorkItems' and description 'List work items based on a WIQL query' indicate data retrieval with no modification or execution of external operations.

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

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

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

listWorkItems 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 Azure Devops — 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 listWorkItems tool do? +

List work items based on a WIQL query. It is categorised as a Read tool in the Azure Devops MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on listWorkItems? +

Register the Azure Devops MCP server in PolicyLayer and add a rule for listWorkItems: 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. Nothing to install.

What risk level is listWorkItems? +

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

Can I rate-limit listWorkItems? +

Yes. Add a rate_limit block to the listWorkItems 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 listWorkItems completely? +

Set action: deny in the PolicyLayer policy for listWorkItems. 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 listWorkItems? +

listWorkItems is provided by the Azure Devops MCP server (ryancardin15/azuredevops-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Azure Devops tool call.

Deterministic rules across all 97 Azure Devops tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

97 Azure Devops 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.