razz_crash_status
Check the current crash round state - phase, multiplier, and players. Use this after play_crash to decide when to cash out. If you're not in the specified room, this will auto-join it so you receive live ticks. Available rooms: __crash_lobby__ (free), __crash_low__, __crash_mid__, __crash_high__.
This record as markdown: /tools/io-github-razz-games-razz/razz-crash-status.md
What razz_crash_status does on Razz Games
AI agents call razz_crash_status to retrieve information from Razz Games without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
roomId | string | — | Crash room ID (default: __crash_lobby__) |
Parameters from the server's own tool schema.
Why razz_crash_status is rated Low
The tool queries and displays current game state (phase, multiplier, players) with no side effects on financial positions, game rules, or data persistence. Auto-joining a room is a passive state transition with no financial or destructive consequences. While the server context involves real SOL wagering, this specific tool only reads status, making it a Read category.
From the tool's definition razz_crash_status: 'Check the current crash round state - phase, multiplier, and players.' This retrieves live game state information without modifying data or executing wagers.
Attacks that exploit this kind of access
The rule that runs razz_crash_status 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_crash_status, this is the rule to start with:
razz_crash_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Razz Games, apply this rule, and every razz_crash_status call is checked against it from then on.
Questions about razz_crash_status
Check the current crash round state - phase, multiplier, and players. Use this after play_crash to decide when to cash out. If you're not in the specified room, this will auto-join it so you receive live ticks. Available rooms: __crash_lobby__ (free), __crash_low__, __crash_mid__, __crash_high__. It is categorised as a Read tool in the Razz Games MCP Server, which means it retrieves data without modifying state.
razz_crash_status accepts 1 parameter: roomId. 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_crash_status: 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_crash_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the razz_crash_status 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_crash_status. 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_crash_status 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.
This server
Across the catalogue