Retrieve a single MantisBT issue by its numeric ID. Returns all issue fields including notes, attachments, and relationships (unless "select" is given). Notes are always included — no separate list_notes call needed.
AI agents call get_issue 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 |
|---|---|---|---|
id | integer | Yes | Numeric issue ID |
select | string | — | Comma-separated list of fields to include in the response (server-side projection, same as list_issues). Significantly reduces response size. Example: "id,summa |
Parameters from the server's own tool schema.
This tool queries and retrieves existing issue data by numeric ID without creating, modifying, deleting, or executing any operations. It has no side effects on the system state. The blast radius of misuse is minimal—an attacker could only access information they might already have permission to view, not modify data or trigger external actions.
From the tool's definition Tool name and description explicitly state "Retrieve a single MantisBT issue" with "all issue fields including notes, attachments, and relationships." The verb "Retrieve" and the read-only nature of fetching issue data without modification confirm this is a…
Attacks that exploit this kind of access
Retrieve a single MantisBT issue by its numeric ID. Returns all issue fields including notes, attachments, and relationships (unless "select" is given). Notes are always included — no separate list_notes call needed. It is categorised as a Read tool in the MantisBT MCP Server MCP Server, which means it retrieves data without modifying state.
get_issue accepts 2 parameters: id, select. Required: id. 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_issue: 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_issue 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 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. 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 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 →