AI agents call deletePost 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 posts is a permanent, irreversible action that cannot be undone through normal means. Once deleted, the post and associated engagement (replies, likes, retweets) are lost. This fits the Destructive category, which covers actions that irreversibly delete or overwrite data.
From the tool's definition Tool name is 'deletePost' and description states 'Delete a post by ID' — the verb 'delete' is explicitly destructive and irreversible.
Documented attack patterns abuse exactly the kind of access deletePost 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 deletePost:
{
"version": "1",
"default": "deny",
"hide": [
"deletePost"
]
}deletePost 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 post by ID. 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 deletePost: 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.
deletePost 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 deletePost 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 deletePost. 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.
deletePost 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.