Gets a list of all fields for a specific work item type. Use this tool when you need to: - See what fields are available for a work item type - Find required fields for creating work items of a specific type - Get reference names for fields to use in queries or updates Args: project: Project ID o...
AI agents call get_work_item_type_fields to retrieve information from MCP Azure DevOps Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that queries the structure of work item types in Azure DevOps. It has no side effects—it simply returns metadata about available fields. The tool does not create, modify, delete, or execute any operations; it only retrieves and displays information.
From the tool's definition The tool 'Gets a list of all fields for a specific work item type' and returns 'A formatted table of all fields with names, reference names, types, and required/read-only status'. It retrieves schema metadata without modifying any data.
Documented attack patterns abuse exactly the kind of access get_work_item_type_fields gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Azure DevOps Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_work_item_type_fields:
{
"version": "1",
"default": "deny",
"tools": {
"get_work_item_type_fields": {}
}
}get_work_item_type_fields is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Gets a list of all fields for a specific work item type. Use this tool when you need to: - See what fields are available for a work item type - Find required fields for creating work items of a specific type - Get reference names for fields to use in queries or updates Args: project: Project ID or project name type_name: The name of the work item type Returns: A formatted table of all fields with names, reference names, types, and required/read-only status. It is categorised as a Read tool in the MCP Azure DevOps Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Azure DevOps Server MCP server in PolicyLayer and add a rule for get_work_item_type_fields: 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 MCP Azure DevOps Server. Nothing to install.
get_work_item_type_fields 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_item_type_fields 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_item_type_fields. 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_item_type_fields is provided by the MCP Azure DevOps Server MCP server (vortiago/mcp-azure-devops). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 MCP Azure DevOps Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
21 MCP Azure DevOps Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.