Retweet a tweet. Requires auth cookies.
AI agents use twitter_retweet to create or update resources in Twitter/X MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Twitter/X MCP Server environment.
Retweeting creates a new public action on the user's Twitter/X account, broadcasting another user's content to all followers. While technically reversible (can be un-retweeted), it constitutes a Write operation. Severity is high because an AI agent could mass-retweet inappropriate, harmful, or embarrassing content on behalf of the account owner, causing significant reputational damage.
From the tool's definition 'Retweet a tweet' - creates a new public repost/share of existing content on the user's profile
Attacks that exploit this kind of access
Retweet a tweet. Requires auth cookies. It is categorised as a Write tool in the Twitter/X MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Twitter/X MCP Server MCP server in PolicyLayer and add a rule for twitter_retweet: 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 Twitter/X MCP Server. Nothing to install.
twitter_retweet 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 twitter_retweet 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 twitter_retweet. 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.
twitter_retweet is provided by the Twitter/X MCP Server MCP server (miles0sage/twitter-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 →