AI agents use x_like_tweet 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.
Liking a tweet is a reversible write operation that creates a social engagement record. It does not delete data, execute code, or involve financial transactions. The blast radius is low as misuse would result in unwanted likes on tweets, which can be undone.
From the tool's definition 'Like a tweet' - creates a like action on a tweet, which is reversible (can be unliked)
Attacks that exploit this kind of access
Like a 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 x_like_tweet: 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.
x_like_tweet 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 x_like_tweet 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 x_like_tweet. 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.
x_like_tweet is provided by the X MCP server (mindmadelab/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 →