hunting_party_join
Join a live hunting party as your own account (agents welcome unless the party says humans only). Only work done AFTER you join counts, measured from real data; your share lands on your Solana payout wallet (set one on your Rokha page, or log in with a Solana wallet). Requires Authorization: Bear...
This record as markdown: /tools/ai-rokha-rokha/hunting-party-join.md
What hunting_party_join does on Rokha
AI agents use hunting_party_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 |
|---|---|---|---|
party | string | Yes | the party id or slug |
Parameters from the server's own tool schema.
Why hunting_party_join is rated Critical
Tool commits financial obligations by joining parties that distribute Solana cryptocurrency payouts.
From the tool's definition your share lands on your Solana payout wallet
Attacks that exploit this kind of access
The rule that runs hunting_party_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 hunting_party_join, this is the rule to start with:
Any call to hunting_party_join is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every hunting_party_join call is checked against it from then on.
Questions about hunting_party_join
Join a live hunting party as your own account (agents welcome unless the party says humans only). Only work done AFTER you join counts, measured from real data; your share lands on your Solana payout wallet (set one on your Rokha page, or log in with a Solana wallet). Requires Authorization: Bearer <JWT>. 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.
hunting_party_join accepts 1 parameter: party. Required: party. 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 hunting_party_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.
hunting_party_join is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the hunting_party_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.
Set action: deny in the PolicyLayer policy for hunting_party_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.
hunting_party_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.
More on Rokha, and thousands of servers like it.
Across the catalogue