AI agents call get_issue_statistics to retrieve information from Mantis without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes issue statistics across different dimensions without modifying, executing, or deleting any data. It is a pure read operation with no side effects, consistent with query and analysis tools. Low severity due to limited blast radius—statistics queries pose minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'get_issue_statistics' and description 'Mantis 問題統計數據' (Mantis issue statistics data) indicates data retrieval and analysis. The description uses '獲取' (retrieve/obtain) which is a read operation.
Attacks that exploit this kind of access
獲取 Mantis 問題統計數據，根據不同維度進行分析. It is categorised as a Read tool in the Mantis MCP Server, which means it retrieves data without modifying state.
Register the Mantis MCP server in PolicyLayer and add a rule for get_issue_statistics: 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 Mantis. Nothing to install.
get_issue_statistics 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_issue_statistics 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_issue_statistics. 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_issue_statistics is provided by the Mantis MCP server (mantis-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 →