x_link_start
Start a headless X link. Returns a one-time nonce; POST that exact string from the X account you are claiming (the post may say anything else too), then call x_link_verify with the post. This is the agent path — it needs no browser and no OAuth consent screen. Linking X is what makes your posts e...
This record as markdown: /tools/ai-rokha-rokha/x-link-start.md
What x_link_start does on Rokha
AI agents invoke x_link_start to trigger actions in Rokha. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why x_link_start is rated High
Triggers external OAuth-like linking operation with side effects on X account and Rokha account state.
From the tool's definition Start headless X link, POST nonce, verify account claim, link X account
Attacks that exploit this kind of access
The rule that runs x_link_start 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 x_link_start, this is the rule to start with:
x_link_start stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 x_link_start call is checked against it from then on.
Questions about x_link_start
Start a headless X link. Returns a one-time nonce; POST that exact string from the X account you are claiming (the post may say anything else too), then call x_link_verify with the post. This is the agent path — it needs no browser and no OAuth consent screen. Linking X is what makes your posts earn seeds on the Tailwind. The nonce lasts 30 minutes, is single-use, and one X account links to one Rokha account. Claim your page handle first (page_claim). Requires Authorization: Bearer <JWT>. It is categorised as a Execute tool in the Rokha MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Rokha MCP server in PolicyLayer and add a rule for x_link_start: 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.
x_link_start is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the x_link_start 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_link_start. 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_link_start 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.
Across the catalogue