network_join_status

Requires a JWT. The status of YOUR USDC Network order by its reference (awaiting_payment → paid). Next when paid: network_me.

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

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What network_join_status does on Rokha

AI agents call network_join_status to retrieve information from Rokha without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`reference`	string	Yes

Parameters from the server's own tool schema.

RISK

Why network_join_status is rated Low

Queries payment status via JWT; retrieves data without modifying, executing, or deleting anything.

From the tool's definition status of YOUR USDC Network order, reference check (awaiting_payment → paid)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

network_join_status Allowed

network_join_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "network_join_status": {}
  }
}

ALLOW ONLY 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_status call is checked against it from then on.

FAQ

Questions about network_join_status

What does the network_join_status tool do? +

Requires a JWT. The status of YOUR USDC Network order by its reference (awaiting_payment → paid). Next when paid: network_me. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.

What parameters does network_join_status accept? +

network_join_status accepts 1 parameter: reference. Required: reference. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on network_join_status? +

Register the Rokha MCP server in PolicyLayer and add a rule for network_join_status: 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_status? +

network_join_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit network_join_status? +

Yes. Add a rate_limit block to the network_join_status 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_status completely? +

Set action: deny in the PolicyLayer policy for network_join_status. 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_status? +

network_join_status 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 →

Across the catalogue

editor_status on 010 Editor → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →