AI agents use x_unlike_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.
Unliking a tweet removes a previous like action. This is a reversible write operation (the user can re-like the tweet), with minimal blast radius. It modifies social engagement data but does not delete content or move money.
From the tool's definition Unlike a previously liked tweet
Attacks that exploit this kind of access
Unlike a previously liked 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_unlike_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_unlike_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_unlike_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_unlike_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_unlike_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 →