Delete a tweet by its ID.
AI agents call delete_tweet to permanently remove resources in MCP-Twikit — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a tweet permanently removes content and cannot be undone. This is a destructive action that irreversibly modifies or removes data, fitting the Destructive category. Severity is high because misuse could delete important tweets, damage reputation, or suppress information. Confidence is high because the intent is unambiguous.
From the tool's definition Tool name is 'delete_tweet' with description 'Delete a tweet by its ID' — the verb 'delete' explicitly indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a tweet by its ID. It is categorised as a Destructive tool in the MCP-Twikit MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP-Twikit MCP server in PolicyLayer and add a rule for 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 MCP-Twikit. Nothing to install.
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 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 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.
delete_tweet is provided by the MCP-Twikit MCP server (zo-valentine/mcp-twikit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →