razz_get_match_info
Get current match info for a spectator/crash room - participants, staking pool, status, crash state, and result. Returns match data when a round is active, plus live crash state (phase, multiplier, players, next round time).
This record as markdown: /tools/io-github-razz-games-razz/razz-get-match-info.md
What razz_get_match_info does on Razz Games
AI agents call razz_get_match_info 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 | — | Room ID to get match info for (defaults to current room) |
Parameters from the server's own tool schema.
Why razz_get_match_info is rated Low
This tool retrieves and queries game state information (participants, staking pool, status, crash state, result, multiplier, players) without side effects. It is purely informational for observation purposes. Although the server context involves real SOL wagering, this specific tool only reads match data—it does not move funds, execute transactions, or trigger game logic.
From the tool's definition Tool description explicitly states it 'Get[s] current match info' and 'Returns match data' for a spectator/crash room. Keywords: 'Get', 'Returns' indicate read-only retrieval.
Attacks that exploit this kind of access
The rule that runs razz_get_match_info 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_get_match_info, this is the rule to start with:
razz_get_match_info 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_get_match_info call is checked against it from then on.
Questions about razz_get_match_info
Get current match info for a spectator/crash room - participants, staking pool, status, crash state, and result. Returns match data when a round is active, plus live crash state (phase, multiplier, players, next round time). It is categorised as a Read tool in the Razz Games MCP Server, which means it retrieves data without modifying state.
razz_get_match_info 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_get_match_info: 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_get_match_info 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_get_match_info 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_get_match_info. 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_get_match_info 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