AI agents use add-delete-bookmark to create or update resources in X — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your X environment.
Bookmarking is a reversible user preference action that modifies data (bookmark list) but does not delete underlying content, execute external operations, or affect financial systems. This is a classic Write operation. Severity is low because the blast radius of accidental bookmarking/unbookmarking is minimal and limited to the authenticated user's preferences.
From the tool's definition Tool name 'add-delete-bookmark' and description 'Add or delete a bookmark for a specific tweet' indicate the tool creates or modifies bookmark state.
Attacks that exploit this kind of access
Add or delete a bookmark for a specific tweet. It is categorised as a Write tool in the X MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the X MCP server in PolicyLayer and add a rule for add-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. Nothing to install.
add-delete-bookmark is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add-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.
Set action: deny in the PolicyLayer policy for add-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.
add-delete-bookmark is provided by the X MCP server (siddheshutd/x-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
add-delete-bookmark is one line of X's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →