Critical Risk →

delete_bookmark

Removes the tweet from bookmarks

How to control delete_bookmark ↓

AI agents call delete_bookmark to permanently remove resources in X (Twitter) MCP server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Deleting a bookmark is an irreversible removal action (the bookmark is gone unless re-added manually). While the blast radius is low (only affects saved bookmarks, not the tweet itself), the action is destructive in nature as it removes data without a recovery mechanism.

From the tool's definition 'Removes the tweet from bookmarks' — permanently removes a saved bookmark entry

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

PolicyLayer is an MCP gateway — it sits between your AI agents and X (Twitter) MCP server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_bookmark:

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

delete_bookmark 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 X (Twitter) MCP server — 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.

Go deeper

What does the delete_bookmark tool do? +

Removes the tweet from bookmarks. It is categorised as a Destructive tool in the X (Twitter) MCP server 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_bookmark? +

Register the X (Twitter) MCP server MCP server in PolicyLayer and add a rule for delete_bookmark: 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 X (Twitter) MCP server. Nothing to install.

What risk level is delete_bookmark? +

delete_bookmark 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_bookmark? +

Yes. Add a rate_limit block to the delete_bookmark 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_bookmark completely? +

Set action: deny in the PolicyLayer policy for delete_bookmark. 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_bookmark? +

delete_bookmark is provided by the X (Twitter) MCP server MCP server (rafaljanicki/x-twitter-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every X (Twitter) MCP server tool call.

Deterministic rules across all 24 X (Twitter) MCP server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

24 X (Twitter) MCP server tools catalogued and risk-classified — across an index of 42,500+ 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.