New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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

SERVERRokha SOURCEhttps://rokha.ai/mcp/jsonrpc
Critical RISK CLASS
Category Financial
Parameters 11 required
Recommended Approval-gatedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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

Questions about hunting_party_join

What does the hunting_party_join tool do? +

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.

What parameters does hunting_party_join accept? +

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

How do I enforce a policy on hunting_party_join? +

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.

What risk level is hunting_party_join? +

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.

Can I rate-limit hunting_party_join? +

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.

How do I block hunting_party_join completely? +

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.

What MCP server provides hunting_party_join? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Rokha's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.