orbitx__orbitx_x_connect
Connect the user's X account to OrbitX so this MCP can post. Returns /auth (Supabase Continue with X) and /x (tweet.write) links.
This record as markdown: /tools/ai-rokha-rokha/orbitx--orbitx-x-connect.md
What orbitx__orbitx_x_connect does on Rokha
AI agents use orbitx__orbitx_x_connect to create or update resources in Rokha, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rokha environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
authCode | string | — | OrbitX authCode from the dashboard paste message or orbitx_auth_link. After auth, pass this on every tool call (required for Grok). Auth contract: signing tools |
Parameters from the server's own tool schema.
Why orbitx__orbitx_x_connect is rated Medium
Grants write access to post tweets on user's X account.
From the tool's definition post, tweet.write, Connect the user's X account
Attacks that exploit this kind of access
The rule that runs orbitx__orbitx_x_connect safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Rokha, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For orbitx__orbitx_x_connect, this is the rule to start with:
orbitx__orbitx_x_connect 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 Rokha, apply this rule, and every orbitx__orbitx_x_connect call is checked against it from then on.
Questions about orbitx__orbitx_x_connect
Connect the user's X account to OrbitX so this MCP can post. Returns /auth (Supabase Continue with X) and /x (tweet.write) links. It is categorised as a Write tool in the Rokha MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
orbitx__orbitx_x_connect accepts 1 parameter: authCode. The full parameter table on this page comes from the server's own tool schema.
Register the Rokha MCP server in PolicyLayer and add a rule for orbitx__orbitx_x_connect: 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 Rokha. Nothing to install.
orbitx__orbitx_x_connect 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 orbitx__orbitx_x_connect 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 orbitx__orbitx_x_connect. 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.
orbitx__orbitx_x_connect is provided by the Rokha MCP server (https://rokha.ai/mcp/jsonrpc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Rokha, and thousands of servers like it.
This server
Across the catalogue