AI agents use twitter_post to create or update resources in Twitter Bridge MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Twitter Bridge MCP environment.
This tool creates new data (tweets) that are published to a social media platform, making it a Write operation. Severity is high because an AI agent could post misinformation, spam, offensive content, or impersonate the account holder at scale, causing reputational damage and platform violations. However, it is reversible (tweets can be deleted), preventing classification as Destructive or critical severity.
From the tool's definition Tool name 'twitter_post' and description 'Post a new tweet' directly indicate creation of new content on Twitter/X platform.
Documented attack patterns abuse exactly the kind of access twitter_post gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Twitter Bridge MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for twitter_post:
{
"version": "1",
"default": "deny",
"tools": {
"twitter_post": {
"limits": [
{
"counter": "twitter_post_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}twitter_post 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.
Post a new tweet. It is categorised as a Write tool in the Twitter Bridge MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Twitter Bridge 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 Bridge MCP. 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 Bridge MCP server (replica882/twitter-bridge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 Twitter Bridge MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
21 Twitter Bridge MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.