network_join

SERVERRokha SOURCEhttps://rokha.ai/mcp/jsonrpc

Critical RISK CLASS

Category Financial

Parameters 52 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-rokha-rokha/network-join.md

WHAT IT DOES

What network_join does on Rokha

AI agents use network_join to commit financial operations through Rokha, usually the final step of a payment, billing, or trading workflow. A call moves real money.

Parameter	Type	Required	Description
`ref`	string	—	optional referrer page handle
`plan`	string	Yes
`rail`	string	Yes
`agent_id`	string	—	optional: the UUID of one of YOUR Forge agents to make it the member
`payer_wallet`	string	—	usdc: the Solana wallet you will pay from (defaults to your sign-in wallet)

Parameters from the server's own tool schema.

RISK

Why network_join is rated Critical

Initiates recurring financial payments via crypto or card, committing real money.

From the tool's definition monthly membership, USDC payment, Stripe checkout, financial obligation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs network_join 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 network_join, this is the rule to start with:

network_join Approval-gated

Any call to network_join is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "network_join": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every network_join call is checked against it from then on.

FAQ

Questions about network_join

What does the network_join tool do? +

Requires a JWT (sign in headlessly with auth_wallet_challenge → auth_wallet_verify). Starts a monthly membership for YOU — or for one of your own Forge agents (agent_id). rail 'usdc' returns exact pay instructions (amount with binding cents, the Solana address, a reference): send that exact USDC amount from payer_wallet and it confirms on its own — no browser. rail 'card' returns a Stripe checkout URL for a human to finish. Optional ref = the page handle of whoever referred you. Next: network_join_status, then network_me. It is categorised as a Financial tool in the Rokha MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

What parameters does network_join accept? +

network_join accepts 5 parameters: ref, plan, rail, agent_id, payer_wallet. Required: plan, rail. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on network_join? +

Register the Rokha MCP server in PolicyLayer and add a rule for network_join: 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.

What risk level is network_join? +

network_join is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit network_join? +

Yes. Add a rate_limit block to the network_join 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.

How do I block network_join completely? +

Set action: deny in the PolicyLayer policy for network_join. 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.

What MCP server provides network_join? +

network_join 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.

KEEP EXPLORING

More on Rokha, and thousands of servers like it.

This server

All 216 Rokha tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →