get_work_items_by_state

Get work items by their state (e.g., Active, New, In Progress, Closed).

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

What get_work_items_by_state does on Azure DevOps MCP Server

AI agents call get_work_items_by_state 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_state needs a policy

This tool performs a read-only query of work items based on state filtering. It has no side effects, does not execute code or commands, does not create or modify data, and does not delete or remove anything. The operation is purely informational retrieval, making it a Read category tool with low severity since misuse would only expose information already accessible within the Azure DevOps project scope.

From the tool's definition Tool name and description indicate a query operation: 'Get work items by their state' retrieves existing work items filtered by state without modifying, creating, or deleting data.

Questions about get_work_items_by_state

What does the get_work_items_by_state tool do? +

Get work items by their state (e.g., Active, New, In Progress, Closed). 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_state? +

Register the Azure DevOps MCP Server MCP server in PolicyLayer and add a rule for get_work_items_by_state: 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_state? +

get_work_items_by_state 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_state? +

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

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

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