List all available work item relation types
AI agents call list_relation_types 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 and enumerates existing relation type definitions from Azure DevOps. It has no side effects, does not modify data, and is purely informational. It falls squarely into the Read category as a list/discovery operation. Severity is low because the blast radius of misuse is minimal—an agent can only view what relation types exist, which is non-sensitive schema information.
From the tool's definition Tool name is 'list_relation_types' and description explicitly states 'List all available work item relation types' — a query operation that retrieves metadata without modification.
Attacks that exploit this kind of access
List all available work item relation types. 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_relation_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_relation_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_relation_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_relation_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_relation_types 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 →