get_work_items_by_query

Get work items using WIQL (Work Item Query Language).

Server Azure DevOps MCP Server jhlia0/azure-devops-mcp
Category Read
Risk class Low
Parameters 00 required

What get_work_items_by_query does on Azure DevOps MCP Server

AI agents call get_work_items_by_query 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.

Why get_work_items_by_query needs a policy

This tool retrieves work items from Azure DevOps via a query interface. WIQL is a read-only query language for filtering and fetching work item data. It has no side effects on the system beyond data retrieval. The sibling tools include write operations (create_work_item, add_work_item_comment) and reads (get_active_work_items, etc.), placing this tool firmly in the Read category with low severity.

From the tool's definition Tool name 'get_work_items_by_query' uses 'get' verb indicating retrieval. Description states 'Get work items using WIQL' — a query language for retrieving data. No modification, deletion, or execution of external operations is described.

Questions about get_work_items_by_query

What does the get_work_items_by_query tool do? +

Get work items using WIQL (Work Item Query Language). It is categorised as a Read tool in the Azure DevOps MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_work_items_by_query? +

Register the Azure DevOps MCP Server MCP server in PolicyLayer and add a rule for get_work_items_by_query: 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.

What risk level is get_work_items_by_query? +

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

Can I rate-limit get_work_items_by_query? +

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

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

get_work_items_by_query 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.