razz_play_crash
Enter a crash game round. Auto-joins the room if you're not in it. This places your bet during the betting phase (~8 seconds). After betting closes, the multiplier starts climbing from 1.00x. Use crash_status to check the current multiplier, then crash_cashout to lock in your profit before it cra...
This record as markdown: /tools/io-github-razz-games-razz/razz-play-crash.md
What razz_play_crash does on Razz Games
AI agents use razz_play_crash 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 |
|---|---|---|---|
roomId | string | — | Crash room ID: __crash_lobby__ (free), __crash_low__, __crash_mid__, __crash_high__ |
wagerAmount | number | — | Amount to wager in SOL (0 or omit for free play, max 0.1) |
Parameters from the server's own tool schema.
Why razz_play_crash is rated Critical
The tool directly places a financial bet using real SOL cryptocurrency. Misuse by an AI agent could result in repeated financial losses up to the maximum wager per round. This clearly falls under Financial as it moves/commits real monetary value, which is the highest severity category.
From the tool's definition 'places your bet', 'real SOL wagering', 'you lose your wager', '0.01-0.1 SOL' — the tool commits real SOL cryptocurrency as a wager in a gambling game
Attacks that exploit this kind of access
The rule that runs razz_play_crash 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_play_crash, this is the rule to start with:
Any call to razz_play_crash 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_play_crash call is checked against it from then on.
Questions about razz_play_crash
Enter a crash game round. Auto-joins the room if you're not in it. This places your bet during the betting phase (~8 seconds). After betting closes, the multiplier starts climbing from 1.00x. Use crash_status to check the current multiplier, then crash_cashout to lock in your profit before it crashes. If you don't cash out before the crash, you lose your wager. Available rooms: __crash_lobby__ (free play, no wagers), __crash_low__ (0.01-0.1 SOL). Max multiplier: 50x. Max 5 wagered players per round. 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_play_crash accepts 2 parameters: roomId, wagerAmount. 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_play_crash: 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_play_crash 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_play_crash 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_play_crash. 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_play_crash 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