Add a tweet to bookmarks
AI agents use bookmarks.add to create or update resources in X MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your X MCP Server environment.
This tool creates a new bookmark record, which is a reversible modification of user data. It does not delete, execute code, or move money, so it falls under Write rather than more severe categories. Severity is medium because misuse could spam a user's bookmarks or bookmark sensitive/inappropriate content, but the action is fully reversible via bookmarks.remove.
From the tool's definition Tool name 'bookmarks.add' and description 'Add a tweet to bookmarks' indicate creation/modification of user data (bookmarks collection). This is a write operation that creates a new association between a user and a tweet.
Attacks that exploit this kind of access
Add a tweet to bookmarks. It is categorised as a Write tool in the X MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the X MCP Server MCP server in PolicyLayer and add a rule for bookmarks.add: 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 MCP Server. Nothing to install.
bookmarks.add 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 bookmarks.add 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 bookmarks.add. 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.
bookmarks.add is provided by the X MCP Server MCP server (tomaitagaki/x-mcp). 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 →