Get all issues filtered by status (e.g.,
AI agents call get_issues_by_status 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 existing issue data by status. It performs no mutations, deletions, or external side effects. The blast radius of misuse is limited to unauthorized information disclosure of work items, which is a low-severity read operation. The confidence is high because the naming convention and context clearly indicate a passive query operation.
From the tool's definition Tool name 'get_issues_by_status' and description 'Get all issues filtered by status' indicate a retrieval/query operation with no modification of data. All sibling tools are read operations (get_*, list_*, query_*).
Attacks that exploit this kind of access
Get all issues filtered by status (e.g.,. 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_issues_by_status: 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_issues_by_status 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_issues_by_status 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_issues_by_status. 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_issues_by_status 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 →