Critical Risk →

delete_draft

Delete a draft tweet or thread

How to control delete_draft ↓

AI agents call delete_draft to permanently remove resources in X(Twitter) MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

This tool permanently removes draft posts from the user's X/Twitter account. While the blast radius is limited (only affects unpublished drafts, not live content), the action cannot be undone. Destructive category applies because deletion is irreversible, even though the severity is medium rather than high since drafts are typically less critical than published content.

From the tool's definition Tool name is 'delete_draft' and description states 'Delete a draft tweet or thread' — the word 'Delete' explicitly indicates irreversible removal of data.

Documented attack patterns abuse exactly the kind of access delete_draft gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and X(Twitter) MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_draft:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_draft"
  ]
}

delete_draft disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register X(Twitter) MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the delete_draft tool do? +

Delete a draft tweet or thread. It is categorised as a Destructive tool in the X(Twitter) MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_draft? +

Register the X(Twitter) MCP Server MCP server in PolicyLayer and add a rule for 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 X(Twitter) MCP Server. Nothing to install.

What risk level is delete_draft? +

delete_draft is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_draft? +

Yes. Add a rate_limit block to the 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.

How do I block delete_draft completely? +

Set action: deny in the PolicyLayer policy for 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.

What MCP server provides delete_draft? +

delete_draft is provided by the X(Twitter) MCP Server MCP server (vidhupv/x-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every X(Twitter) MCP Server tool call.

Deterministic rules across all 5 X(Twitter) MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

5 X(Twitter) MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.