Delete a draft by its key. Requires the current sequence number from list/get operations to prevent conflicts.
AI agents call discourse_delete_draft to permanently remove resources in Discourse MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data (draft content) and cannot be undone. While the blast radius is limited to draft content rather than published posts, deletion is inherently destructive. The medium severity reflects that drafts are typically work-in-progress and less critical than published content, but the action is still permanent and could result in loss of user work if an agent misuses it.
From the tool's definition Tool name is 'discourse_delete_draft' with description stating 'Delete a draft by its key'. The verb 'Delete' combined with the action of removing a draft irreversibly places this in the Destructive category.
Attacks that exploit this kind of access
Delete a draft by its key. Requires the current sequence number from list/get operations to prevent conflicts. It is categorised as a Destructive tool in the Discourse MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Discourse MCP server in PolicyLayer and add a rule for discourse_delete_draft: 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 Discourse MCP. Nothing to install.
discourse_delete_draft 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 discourse_delete_draft 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 discourse_delete_draft. 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.
discourse_delete_draft is provided by the Discourse MCP server (king-of-the-grackles/discourse-mcp). 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 →