x-twitter.delete_post
Delete a post published by a connected X account. Call x-twitter.connected_accounts first. Pass user_id or user_name to target a specific account, or omit both to use the default account. Cost = 25 tokens.
This record as markdown: /tools/io-github-vee3io-vee3/x-twitter.delete-post.md
What x-twitter.delete_post does on Vee3
AI agents call x-twitter.delete_post to permanently remove resources in Vee3, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
post_id | string | Yes | Numeric id of the post to delete. |
user_id | object | — | Numeric X user id from x-twitter.connected_accounts. Pass user_id or user_name to target a specific account, not both. Omit both to use the default account. |
user_name | object | — | X handle from x-twitter.connected_accounts, with or without a leading @. Pass user_id or user_name to target a specific account, not both. Omit both to use the |
Parameters from the server's own tool schema.
Why x-twitter.delete_post is rated Critical
The tool explicitly deletes published content from an X (Twitter) account. Deletion of posts is irreversible — once deleted, the post, its engagement metrics, replies, and reach are permanently lost. This qualifies as Destructive with high severity since an AI agent could remove public-facing content from a connected social media account without the ability to undo the action.
From the tool's definition Delete a post published by a connected X account
Attacks that exploit this kind of access
The rule that runs x-twitter.delete_post safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vee3, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For x-twitter.delete_post, this is the rule to start with:
x-twitter.delete_post is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Vee3, apply this rule, and every x-twitter.delete_post call is checked against it from then on.
Questions about x-twitter.delete_post
Delete a post published by a connected X account. Call x-twitter.connected_accounts first. Pass user_id or user_name to target a specific account, or omit both to use the default account. Cost = 25 tokens. It is categorised as a Destructive tool in the Vee3 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
x-twitter.delete_post accepts 3 parameters: post_id, user_id, user_name. Required: post_id. The full parameter table on this page comes from the server's own tool schema.
Register the Vee3 MCP server in PolicyLayer and add a rule for x-twitter.delete_post: 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 Vee3. Nothing to install.
x-twitter.delete_post 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 x-twitter.delete_post 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 x-twitter.delete_post. 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.
x-twitter.delete_post is provided by the Vee3 MCP server (https://mcp.vee3.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vee3, and thousands of servers like it.
Across the catalogue