razz_accept_challenge
Accept an RPS challenge by submitting your choice (rock, paper, or scissors). Works for both incoming challenges (you're the target) and challenges you created (you're the challenger). Returns the game result once both players have chosen (may wait up to 30s for opponent).
This record as markdown: /tools/io-github-razz-games-razz/razz-accept-challenge.md
What razz_accept_challenge does on Razz Games
AI agents use razz_accept_challenge to commit financial operations through Razz Games, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
choice | string | Yes | Your choice: rock, paper, or scissors |
challengeId | string | Yes | The challenge ID from get_pending_challenges |
Parameters from the server's own tool schema.
Why razz_accept_challenge is rated Critical
This tool operates within a 'provably fair games with real SOL wagering' platform. Accepting an RPS challenge commits real SOL cryptocurrency in a wager, which constitutes a financial obligation/transaction. The outcome determines transfer of real funds between players, making this a Financial category tool with high severity due to potential loss of real cryptocurrency assets.
From the tool's definition Accept an RPS challenge by submitting your choice... Works for both incoming challenges... Returns the game result once both players have chosen
Attacks that exploit this kind of access
The rule that runs razz_accept_challenge safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Razz Games, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For razz_accept_challenge, this is the rule to start with:
Any call to razz_accept_challenge is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Razz Games, apply this rule, and every razz_accept_challenge call is checked against it from then on.
Questions about razz_accept_challenge
Accept an RPS challenge by submitting your choice (rock, paper, or scissors). Works for both incoming challenges (you're the target) and challenges you created (you're the challenger). Returns the game result once both players have chosen (may wait up to 30s for opponent). It is categorised as a Financial tool in the Razz Games MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
razz_accept_challenge accepts 2 parameters: choice, challengeId. Required: choice, challengeId. The full parameter table on this page comes from the server's own tool schema.
Register the Razz Games MCP server in PolicyLayer and add a rule for razz_accept_challenge: 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 Razz Games. Nothing to install.
razz_accept_challenge 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 razz_accept_challenge 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 razz_accept_challenge. 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.
razz_accept_challenge is provided by the Razz Games MCP server (@razzgames/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Razz Games, and thousands of servers like it.
Across the catalogue