removeBookmark

THE RISK

Critical Risk

Why removeBookmark needs a policy

Removing a bookmark is an irreversible deletion of saved content. While the original post remains, the bookmark association is permanently deleted without an undo mechanism, making this Destructive rather than Write.

From the tool's definition Remove a bookmark on behalf of the authenticated user

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

POLICY

How to control removeBookmark

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "removeBookmark"
  ]
}

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

Create a free account and register X Com MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More X Com MCP Server tools

Destructive deletePost Delete a post by ID Destructive deleteRetweet Remove a retweet on behalf of the authenticated user Write hideReply Hide or unhide a reply to a post Write bookmarkPost Bookmark a post on behalf of the authenticated user Write createPost Create a new post on behalf of the authenticated user Write createRetweet Retweet a post on behalf of the authenticated user Write likePost Like a post on behalf of the authenticated user Write unlikePost Unlike a post on behalf of the authenticated user

All 21 X Com MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in X Com MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about removeBookmark

What does the removeBookmark tool do? +

Remove a bookmark on behalf of the authenticated user. It is categorised as a Destructive tool in the X Com 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 removeBookmark? +

Register the X Com MCP Server MCP server in PolicyLayer and add a rule for removeBookmark: 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 Com MCP Server. Nothing to install.

What risk level is removeBookmark? +

removeBookmark 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 removeBookmark? +

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

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

removeBookmark is provided by the X Com MCP Server MCP server (tiovikram/x.com-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 Com MCP Server tool call.

Start from X Com MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →