AI agents call delete_tweet 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.
This tool permanently removes data (a tweet) that cannot be undone. Deletion is the hallmark of the Destructive category. While the blast radius is primarily limited to the authenticated user's own tweets, the irreversible nature and potential for unintended deletion of important content elevates this to 'high' severity. Confidence is very high given the explicit 'Delete' language in both name and description.
From the tool's definition Tool name 'delete_tweet' and description 'Delete a tweet by its ID' explicitly perform irreversible deletion of user-generated content.
Documented attack patterns abuse exactly the kind of access delete_tweet 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_tweet:
{
"version": "1",
"default": "deny",
"hide": [
"delete_tweet"
]
}delete_tweet disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a tweet by its ID. 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.
Register the X (Twitter) MCP server MCP server in PolicyLayer and add a rule for delete_tweet: 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.
delete_tweet 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_tweet 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_tweet. 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_tweet is provided by the X (Twitter) MCP server MCP server (rafaljanicki/x-twitter-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 24 X (Twitter) MCP server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
24 X (Twitter) MCP server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.