Query tickets using natural language. Supports filtering by state, development links (commits, pull requests), assignee, tags, and combinations. Examples:
AI agents call query_tickets 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 filters ticket data from Azure DevOps based on various criteria. It performs read-only queries with no side effects—no creation, modification, deletion, or code execution. The filtering capabilities (state, assignee, tags, development links) are all passive searches over existing data.
From the tool's definition Tool name 'query_tickets' and description explicitly state it 'Query tickets using natural language' with filtering capabilities (state, assignee, tags, commits, pull requests).
Attacks that exploit this kind of access
Query tickets using natural language. Supports filtering by state, development links (commits, pull requests), assignee, tags, and combinations. Examples:. 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 query_tickets: 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.
query_tickets 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 query_tickets 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 query_tickets. 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.
query_tickets is provided by the Azure DevOps MCP Server MCP server (linhdangopti/mcpserver). 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 →