Permanently delete a MantisBT issue. This action is irreversible.
AI agents call delete_issue to permanently remove resources in MantisBT MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | integer | Yes | Numeric issue ID to delete |
Parameters from the server's own tool schema.
This tool irreversibly removes data (an entire issue record) from the system. Destructive actions are those that cannot be undone, which is explicitly stated in the description. While the blast radius depends on the importance of the deleted issue, the permanent and irreversible nature of the operation makes this a destructive action with high severity risk to data integrity.
From the tool's definition Tool description explicitly states "Permanently delete a MantisBT issue" and "This action is irreversible." The verb "delete" combined with "permanently" and "irreversible" clearly indicates data destruction that cannot be undone.
Attacks that exploit this kind of access
Permanently delete a MantisBT issue. This action is irreversible. It is categorised as a Destructive tool in the MantisBT MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_issue accepts 1 parameter: id. 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 delete_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.
delete_issue is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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 →