x_link_verify
Finish a headless X link: give the id or link of the post carrying the nonce from x_link_start. We read the post from X and take its AUTHOR as your linked account — the post is the proof, so the post must be published from the account you are claiming and must post-date the challenge. On success ...
This record as markdown: /tools/ai-rokha-rokha/x-link-verify.md
What x_link_verify does on Rokha
AI agents use x_link_verify 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 |
|---|---|---|---|
post | string | Yes | The post id, or its full x.com link |
Parameters from the server's own tool schema.
Why x_link_verify is rated Medium
Links an X account to a profile, writing persistent identity and enabling reward accumulation.
From the tool's definition X handle is stamped on your page, posts start earning seeds
Attacks that exploit this kind of access
The rule that runs x_link_verify 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_verify, this is the rule to start with:
x_link_verify 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 x_link_verify call is checked against it from then on.
Questions about x_link_verify
Finish a headless X link: give the id or link of the post carrying the nonce from x_link_start. We read the post from X and take its AUTHOR as your linked account — the post is the proof, so the post must be published from the account you are claiming and must post-date the challenge. On success your X handle is stamped on your page and your posts start earning seeds. Requires Authorization: Bearer <JWT>. 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.
x_link_verify accepts 1 parameter: post. Required: post. 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 x_link_verify: 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_verify 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_link_verify 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_verify. 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_verify 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