list_work_item_types
A read tool on the Azure DevOps MCP server.
This record as markdown: /tools/abdelrhmansror-azuredevopsmcp/list-work-item-types.md
What list_work_item_types does on Azure DevOps MCP Server
AI agents call list_work_item_types to retrieve information from Azure DevOps MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_work_item_types is rated Low
The 'list' prefix is a strong signal of a Read category tool. It retrieves metadata about work item types without modifying or executing operations. Even if an AI agent misuses this tool, it can only read type information with no destructive, financial, or side-effect consequences. The empty description lowers confidence slightly from 0.9 to 0.85, but the naming pattern and server context provide sufficient evidence.
From the tool's definition Tool name 'list_work_item_types' indicates a listing/retrieval operation. No description provided, but naming convention and context among sibling tools (which include create, link, and comment operations) strongly suggests this is a query-only tool that…
Attacks that exploit this kind of access
The rule that runs list_work_item_types safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Azure DevOps MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_work_item_types, this is the rule to start with:
list_work_item_types is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Azure DevOps MCP Server, apply this rule, and every list_work_item_types call is checked against it from then on.
Questions about list_work_item_types
list_work_item_types is a read tool on the Azure DevOps MCP Server MCP server. 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 list_work_item_types: 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.
list_work_item_types 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 list_work_item_types 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 list_work_item_types. 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.
list_work_item_types is provided by the Azure DevOps MCP Server MCP server (abdelrhmansror/azuredevopsmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Azure DevOps MCP Server, and thousands of servers like it.
This server
Across the catalogue