Post a tweet to X (Twitter)
AI agents use post_tweet to create or update resources in X MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your X MCP Server environment.
This tool creates new, reversible content on X/Twitter. It is not destructive (tweets can be deleted), not financial, and not execute/arbitrary code. The severity is medium rather than low because unauthorized posting could damage reputation, spread misinformation, or violate platform policies, with potential reach to a large audience.
From the tool's definition Tool name 'post_tweet' and description 'Post a tweet to X (Twitter)' indicate creation of new content on a public platform. The server description confirms it 'Supports posting tweets' as a write operation.
Attacks that exploit this kind of access
Post a tweet to X (Twitter). It is categorised as a Write tool in the X MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the X MCP Server MCP server in PolicyLayer and add a rule for post_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 MCP Server. Nothing to install.
post_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 post_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 post_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.
post_tweet is provided by the X MCP Server MCP server (krishna-paulraj/x-mcp-server). 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 →