razz_create_challenge
Challenge another player to RPS. You must be in the same room as the target. Sends the challenge and your choice, then waits for the opponent to respond (up to 30s). If they don't respond, the challenge times out and any wager is refunded.
This record as markdown: /tools/io-github-razz-games-razz/razz-create-challenge.md
What razz_create_challenge does on Razz Games
AI agents use razz_create_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 |
roomId | string | — | Room ID where the target is (uses current room if omitted) |
targetId | string | Yes | Account ID of the player to challenge |
wagerAmount | number | — | Amount to wager in SOL (0 or omit for free play) |
Parameters from the server's own tool schema.
Why razz_create_challenge is rated Critical
This tool initiates a real-money wager in SOL cryptocurrency as part of a game challenge. Committing a financial stake against another player constitutes a financial obligation/transaction. If the opponent accepts, real SOL changes hands. Even if refunded on timeout, the act of sending the challenge locks up real funds, placing this firmly in the Financial category, which supersedes Execute or Write.
From the tool's definition "real SOL wagering", "any wager is refunded" (implies real wager committed), "Challenge another player to RPS"
Attacks that exploit this kind of access
The rule that runs razz_create_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_create_challenge, this is the rule to start with:
Any call to razz_create_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_create_challenge call is checked against it from then on.
Questions about razz_create_challenge
Challenge another player to RPS. You must be in the same room as the target. Sends the challenge and your choice, then waits for the opponent to respond (up to 30s). If they don't respond, the challenge times out and any wager is refunded. 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_create_challenge accepts 4 parameters: choice, roomId, targetId, wagerAmount. Required: choice, targetId. 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_create_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_create_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_create_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_create_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_create_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