twitter_delete_tweet
Delete a tweet by ID
This record as markdown: /tools/io-github-alifanov-scopegate/twitter-delete-tweet.md
What twitter_delete_tweet does on ScopeGate
AI agents call twitter_delete_tweet to permanently remove resources in ScopeGate, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why twitter_delete_tweet is rated Critical
Deleting a tweet is a destructive action that cannot be undone. Once deleted, the tweet is permanently removed and cannot be recovered. This represents an irreversible loss of data/content.
From the tool's definition The tool name is 'twitter_delete_tweet' and the description states 'Delete a tweet by ID'. The verb 'delete' and the action of removing a tweet are irreversible operations.
Attacks that exploit this kind of access
The rule that runs twitter_delete_tweet safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For twitter_delete_tweet, this is the rule to start with:
twitter_delete_tweet 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 ScopeGate, apply this rule, and every twitter_delete_tweet call is checked against it from then on.
Questions about twitter_delete_tweet
Delete a tweet by ID. It is categorised as a Destructive tool in the ScopeGate MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ScopeGate MCP server in PolicyLayer and add a rule for twitter_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 ScopeGate. Nothing to install.
twitter_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 twitter_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 twitter_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.
twitter_delete_tweet is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScopeGate, and thousands of servers like it.
Across the catalogue