AI agents call get_issue_by_id 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 queries and retrieves existing issue data from a Mantis bug tracking system without modifying, deleting, or executing any operations. It is purely informational, making it a Read operation with low severity risk.
From the tool's definition Tool name 'get_issue_by_id' and description '根據 ID 獲取 Mantis 問題詳情' (Get Mantis issue details by ID) indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
根據 ID 獲取 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_by_id: 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_by_id 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_by_id 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_by_id. 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_by_id 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 →