Create a new post on behalf of the authenticated user
AI agents use createPost 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.
The tool creates new content on X.com (formerly Twitter) under the authenticated user's identity. This is a Write operation because it creates data reversibly (posts can be deleted). Severity is high because an AI agent could generate harmful, misleading, or offensive posts at scale, damaging the user's reputation or violating platform policies.
From the tool's definition Tool description explicitly states 'Create a new post on behalf of the authenticated user' – a reversible creation operation that modifies the user's account state.
Documented attack patterns abuse exactly the kind of access createPost 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 createPost:
{
"version": "1",
"default": "deny",
"tools": {
"createPost": {
"limits": [
{
"counter": "createpost_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}createPost 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.
Create a new 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 createPost: 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.
createPost 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 createPost 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 createPost. 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.
createPost 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.