Discover available fields in Azure DevOps (compact output with filtering)
AI agents call discover_fields 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 schema information about Azure DevOps fields. It performs a read-only discovery operation with no side effects, no data modification, and no execution of arbitrary operations. The filtering capability is for refining the output of the read operation, not for performing mutations or destructive actions. This is consistent with the 'Read' category for tools that retrieve or query data.
From the tool's definition Tool name 'discover_fields' and description 'Discover available fields in Azure DevOps (compact output with filtering)' indicate a query/introspection operation that retrieves metadata about available fields without modifying data.
Attacks that exploit this kind of access
Discover available fields in Azure DevOps (compact output with filtering). 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 discover_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 Azure DevOps MCP Server. Nothing to install.
discover_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 discover_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 discover_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.
discover_fields is provided by the Azure DevOps MCP Server MCP server (jaybird-us/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 →