razz_get_opponent_history
Get a player's recent game history to analyze their play patterns. Returns recent results with game-specific details (e.g. crash cashout multipliers, dice rolls, RPS choices). Use this to study opponents before or during games.
This record as markdown: /tools/io-github-razz-games-razz/razz-get-opponent-history.md
What razz_get_opponent_history does on Razz Games
AI agents call razz_get_opponent_history 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 |
|---|---|---|---|
limit | number | — | Number of recent games to return (default: 20) |
gameType | string | — | Filter by game type: crash, dice, flip, rps (default: all) |
playerId | string | Yes | Account ID of the player to look up |
Parameters from the server's own tool schema.
Why razz_get_opponent_history is rated Low
This tool retrieves historical game data about other players. While the broader server involves financial wagering (SOL), this specific tool only queries and returns information—it does not move money, execute game logic, delete data, or trigger external operations.
From the tool's definition Tool description explicitly states it 'Get[s] a player's recent game history' and 'Returns recent results' — purely retrieval operations with 'no side effects' per the Read definition.
Attacks that exploit this kind of access
The rule that runs razz_get_opponent_history 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_opponent_history, this is the rule to start with:
razz_get_opponent_history 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_opponent_history call is checked against it from then on.
Questions about razz_get_opponent_history
Get a player's recent game history to analyze their play patterns. Returns recent results with game-specific details (e.g. crash cashout multipliers, dice rolls, RPS choices). Use this to study opponents before or during games. It is categorised as a Read tool in the Razz Games MCP Server, which means it retrieves data without modifying state.
razz_get_opponent_history accepts 3 parameters: limit, gameType, playerId. Required: playerId. 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_opponent_history: 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_opponent_history 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_opponent_history 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_opponent_history. 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_opponent_history 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