Post a tweet to Twitter
AI agents use twitter_post to create or update resources in Twitter MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Twitter MCP Server environment.
Posting to Twitter is a Write operation that creates public content. Severity is high because a compromised agent could spam, impersonate, or damage reputation by posting without authorization. It's Write rather than Execute because the tool's primary effect is content creation (not running arbitrary code), and while tweets are public, they are not inherently destructive in the sense of deletion or financial harm.
From the tool's definition Tool description states 'Post a tweet to Twitter' — this creates new content on the platform irreversibly from a user perspective, and the server description confirms 'posting tweets' via 'browser automation'.
Attacks that exploit this kind of access
Post a tweet to Twitter. It is categorised as a Write tool in the Twitter MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Twitter MCP Server MCP server in PolicyLayer and add a rule for twitter_post: 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 MCP Server. Nothing to install.
twitter_post 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_post 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_post. 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_post is provided by the Twitter MCP Server MCP server (kylejeong2/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 →