AI agents call delete_scheduled_tweet to permanently remove resources in Twikit — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a scheduled tweet is a destructive action that cannot be undone—the scheduled tweet is permanently removed from the user's queue. Although the description is empty, the tool name unambiguously describes deletion of a scheduled resource. This ranks higher than Write (which is reversible) and is characteristic of Destructive operations.
From the tool's definition Tool name 'delete_scheduled_tweet' with verb 'delete' indicates irreversible removal of data (a scheduled tweet). The sibling tool context confirms this server manages tweet lifecycle operations including deletion.
Documented attack patterns abuse exactly the kind of access delete_scheduled_tweet gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Twikit, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_scheduled_tweet:
{
"version": "1",
"default": "deny",
"hide": [
"delete_scheduled_tweet"
]
}delete_scheduled_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_scheduled_tweet. It is categorised as a Destructive tool in the Twikit MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Twikit MCP server in PolicyLayer and add a rule for delete_scheduled_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 Twikit. Nothing to install.
delete_scheduled_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_scheduled_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_scheduled_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_scheduled_tweet is provided by the Twikit MCP server (tangivis/twitter-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Twikit, 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.
59 Twikit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.