x_action
Use the connected X/Twitter account to read, search, and post.
This record as markdown: /tools/cowork-os/x-action.md
What x_action does on CoWork OS
AI agents use x_action to create or update resources in CoWork OS, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CoWork OS environment.
Why x_action is rated Medium
The tool supports read and search (lower severity) but also posting to a connected X/Twitter account, which is a Write operation with public social-media impact. Misuse could result in unauthorized public posts, reputation damage, or spam. Per the severity hierarchy, Write dominates Read, and public posting on social media carries high blast radius.
From the tool's definition 'post' — the tool can post content to X/Twitter using a connected account
Attacks that exploit this kind of access
The rule that runs x_action safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For x_action, this is the rule to start with:
x_action 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.
The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every x_action call is checked against it from then on.
Questions about x_action
Use the connected X/Twitter account to read, search, and post. It is categorised as a Write tool in the CoWork OS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CoWork OS MCP server in PolicyLayer and add a rule for x_action: 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 CoWork OS. Nothing to install.
x_action 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 x_action 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 x_action. 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.
x_action is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CoWork OS, and thousands of servers like it.
This server
Across the catalogue