Remove a retweet on behalf of the authenticated user
AI agents call deleteRetweet to permanently remove resources in X Com MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of user-generated social media actions is destructive because it irreversibly removes data. While the blast radius is limited to the authenticated user's retweet history (not system-wide data deletion), the action cannot be reversed and represents a permanent modification of public social state.
From the tool's definition Tool name is 'deleteRetweet' and description states 'Remove a retweet on behalf of the authenticated user'. The verb 'Remove' indicates deletion of data (a social media action) that cannot be undone—once a retweet is deleted, the action is irreversible.
Documented attack patterns abuse exactly the kind of access deleteRetweet gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and X Com MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for deleteRetweet:
{
"version": "1",
"default": "deny",
"hide": [
"deleteRetweet"
]
}deleteRetweet 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.
Remove a retweet on behalf of the authenticated user. It is categorised as a Destructive tool in the X Com MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the X Com MCP Server MCP server in PolicyLayer and add a rule for deleteRetweet: 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 Com MCP Server. Nothing to install.
deleteRetweet 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 deleteRetweet 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 deleteRetweet. 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.
deleteRetweet is provided by the X Com MCP Server MCP server (tiovikram/x.com-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from X Com MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 X Com MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.