AI agents call get_work_item_type_field to retrieve information from Ado without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on naming convention, this tool queries or retrieves field type information from Azure DevOps work items without modifying data. No side effects are apparent. The empty description prevents higher confidence, but the 'get_' prefix and context among sibling tools (which include write/destructive operations like delete_work_item) suggests this is a safe read operation.
From the tool's definition Tool name 'get_work_item_type_field' indicates retrieval of metadata about work item field types; the 'get_' prefix and lack of action verbs suggest a read operation. Description is empty, reducing confidence.
Attacks that exploit this kind of access
get_work_item_type_field. It is categorised as a Read tool in the Ado MCP Server, which means it retrieves data without modifying state.
Register the Ado MCP server in PolicyLayer and add a rule for get_work_item_type_field: 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 Ado. Nothing to install.
get_work_item_type_field 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_field 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_field. 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_field is provided by the Ado MCP server (raboley/ado-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 →