Counts Azure DevOps tickets by state (New, Active, Resolved, Closed)
AI agents call get_ticket_count 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 only queries and aggregates data about ticket states without any side effects. It matches the Read category pattern of retrieval operations (get, query, fetch). Low severity because misuse would only expose summary statistics, not sensitive detailed data, and has no destructive or operational impact.
From the tool's definition Tool retrieves counts of tickets grouped by state (New, Active, Resolved, Closed). The operation is a query that 'counts' and does not modify, delete, or execute external operations.
Attacks that exploit this kind of access
Counts Azure DevOps tickets by state (New, Active, Resolved, Closed). 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 get_ticket_count: 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.
get_ticket_count 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_ticket_count 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_ticket_count. 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_ticket_count is provided by the Azure DevOps MCP Server MCP server (saktheeswar/azure_devops_mcp_server). 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 →