Retweet a post on behalf of the authenticated user
AI agents use createRetweet to create or update resources in X Com MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your X Com MCP Server environment.
This tool creates new data (a retweet engagement) on behalf of the user, which is a Write operation. It is not Destructive because retweets are reversible (can be undone). It is not Execute because it does not run arbitrary code or scripts—it performs a specific, well-defined social media action.
From the tool's definition The tool description states it will 'Retweet a post on behalf of the authenticated user', which creates a new retweet action on X.com.
Documented attack patterns abuse exactly the kind of access createRetweet gives an agent:
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 createRetweet:
{
"version": "1",
"default": "deny",
"tools": {
"createRetweet": {
"limits": [
{
"counter": "createretweet_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}createRetweet stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retweet a post on behalf of the authenticated user. It is categorised as a Write tool in the X Com MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the X Com MCP Server MCP server in PolicyLayer and add a rule for createRetweet: 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.
createRetweet 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 createRetweet 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 createRetweet. 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.
createRetweet 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.
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.
Free to start. No card required.
21 X Com MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.