Permanently delete a note from a MantisBT issue. This action is irreversible — deleted notes cannot be recovered. Returns a plain-text confirmation message on success. Returns an error if the note does not exist or the current user lacks permission to delete it (MantisBT enforces access control: ...
AI agents call delete_note 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 |
|---|---|---|---|
note_id | integer | Yes | Numeric note ID to delete — obtain from get_issue (notes[].id) or list_notes |
issue_id | integer | Yes | Numeric issue ID that owns the note — use get_issue or list_notes to identify this value |
Parameters from the server's own tool schema.
This tool irreversibly deletes data (notes) from a MantisBT issue and cannot be undone. While access controls mitigate some risk (users typically delete only their own notes), an agent with elevated permissions could delete notes belonging to others.
From the tool's definition Tool description explicitly states 'Permanently delete a note' and 'This action is irreversible — deleted notes cannot be recovered.' The function name 'delete_note' combined with these descriptors clearly indicates irreversible data deletion.
Attacks that exploit this kind of access
Permanently delete a note from a MantisBT issue. This action is irreversible — deleted notes cannot be recovered. Returns a plain-text confirmation message on success. Returns an error if the note does not exist or the current user lacks permission to delete it (MantisBT enforces access control: users can typically only delete their own notes unless they have manager-level access or higher). Prerequisites: obtain note_id from list_notes or from get_issue (notes[].id); obtain issue_id from the same source. 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_note accepts 2 parameters: note_id, issue_id. Required: note_id, issue_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_note: 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_note 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_note 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_note. 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_note 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 →