Critical Risk →

delete_dm

Delete a direct message by ID.

How to control delete_dm ↓

What delete_dm does on Twikit

AI agents call delete_dm 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.

Critical Risk

Why delete_dm needs a policy

Deleting a direct message is an irreversible operation that permanently removes data from the user's account. This falls squarely into the Destructive category, which covers actions that cannot be undone.

From the tool's definition Tool name is 'delete_dm' with description 'Delete a direct message by ID.' The verb 'delete' and the irreversible nature of removing a direct message constitute a destructive action.

Documented attack patterns abuse exactly the kind of access delete_dm gives an agent:

How to control delete_dm

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_dm:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_dm"
  ]
}

delete_dm disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Twikit — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_dm

What does the delete_dm tool do? +

Delete a direct message by ID. 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.

How do I enforce a policy on delete_dm? +

Register the Twikit MCP server in PolicyLayer and add a rule for delete_dm: 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.

What risk level is delete_dm? +

delete_dm is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_dm? +

Yes. Add a rate_limit block to the delete_dm 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.

How do I block delete_dm completely? +

Set action: deny in the PolicyLayer policy for delete_dm. 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.

What MCP server provides delete_dm? +

delete_dm 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.

Enforce policy on every Twikit tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.