Retrieve multiple MantisBT issues by their numeric IDs in a single MCP call. Requests run in parallel (max 5 concurrent). Missing or inaccessible IDs return null at their array position — the call never fails due to individual missing IDs. Response includes "requested", "found", and "failed" coun...
AI agents call get_issues to retrieve information from MantisBT MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
ids | array | Yes | Array of numeric issue IDs to fetch (1–50). null is returned per ID on 404/403/error instead of failing the whole call. |
Parameters from the server's own tool schema.
The tool's sole function is to retrieve issue data from MantisBT by ID. It has no destructive, write, financial, or code execution capabilities. Retrieving existing issues poses minimal risk; the tool returns null for inaccessible IDs and never fails the request itself. This is a straightforward read operation with limited blast radius even if misused—an agent would only be able to view issues it has access to.
From the tool's definition Tool description states 'Retrieve multiple MantisBT issues by their numeric IDs' and explicitly describes retrieving/querying data without side effects. No modification, deletion, or execution of code/commands.
Attacks that exploit this kind of access
Retrieve multiple MantisBT issues by their numeric IDs in a single MCP call. Requests run in parallel (max 5 concurrent). Missing or inaccessible IDs return null at their array position — the call never fails due to individual missing IDs. Response includes "requested", "found", and "failed" counters for quick validation. It is categorised as a Read tool in the MantisBT MCP Server MCP Server, which means it retrieves data without modifying state.
get_issues accepts 1 parameter: ids. Required: ids. The full parameter table on this page comes from the server's own tool schema.
Register the MantisBT MCP Server MCP server in PolicyLayer and add a rule for get_issues: 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 MantisBT MCP Server. Nothing to install.
get_issues 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 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. 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 is provided by the MantisBT MCP Server MCP server (@dpesch/mantisbt-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 →