get_work_items_by_type
AI agents call get_work_items_by_type 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 or queries work items filtered by type from Azure DevOps. The 'get_' prefix and 'by_type' qualifier indicate a read-only data retrieval operation with no side effects. Confidence is high due to consistent naming conventions across the sibling toolset. The missing description slightly reduces confidence, but the pattern is clear.
From the tool's definition Tool name 'get_work_items_by_type' indicates a retrieval/query operation. The sibling tools 'get_active_work_items', 'get_closed_work_items', 'get_backlog_items', etc. are all read-only retrieval operations, consistent with this tool's function.
Attacks that exploit this kind of access
get_work_items_by_type. 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 get_work_items_by_type: 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.
get_work_items_by_type 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 get_work_items_by_type 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 get_work_items_by_type. 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.
get_work_items_by_type 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.
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 →