Low Risk

getWorkItemTypeFields

Get fields for a work item type

How to control getWorkItemTypeFields ↓

AI agents call getWorkItemTypeFields to retrieve information from Azure Devops without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves metadata about work item type fields in Azure DevOps. It performs a query/fetch operation that does not create, modify, delete, or execute any actions. The response is informational and read-only, making it a Read category tool with low severity since metadata disclosure poses minimal risk.

From the tool's definition Tool name 'getWorkItemTypeFields' and description 'Get fields for a work item type' indicate a retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access getWorkItemTypeFields gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Azure Devops, and nothing reaches the server without passing your rules. This is the rule we recommend for getWorkItemTypeFields:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "getWorkItemTypeFields": {}
  }
}

getWorkItemTypeFields is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Azure Devops — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the getWorkItemTypeFields tool do? +

Get fields for a work item type. It is categorised as a Read tool in the Azure Devops MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getWorkItemTypeFields? +

Register the Azure Devops MCP server in PolicyLayer and add a rule for getWorkItemTypeFields: 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. Nothing to install.

What risk level is getWorkItemTypeFields? +

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

Can I rate-limit getWorkItemTypeFields? +

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

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

getWorkItemTypeFields is provided by the Azure Devops MCP server (ryancardin15/azuredevops-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Azure Devops tool call.

Deterministic rules across all 97 Azure Devops tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

97 Azure Devops tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.