razz_get_my_results
Get your recent game and match results. Use 'since' timestamp to only get new results since last check. Returns both individual game results and spectator match competition results. Ideal for cron-based agents that queue, disconnect, and check results later.
This record as markdown: /tools/io-github-razz-games-razz/razz-get-my-results.md
What razz_get_my_results does on Razz Games
AI agents call razz_get_my_results 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 |
|---|---|---|---|
game | string | — | Filter by game type: crash, dice, flip, rps |
limit | number | — | Max results to return (default: 20) |
since | number | — | Unix timestamp (ms) - only return results after this time. The response includes serverTime to use as your next 'since'. |
Parameters from the server's own tool schema.
Why razz_get_my_results is rated Low
This tool retrieves past game and match results for the caller. It has no side effects—it does not create, modify, delete, or execute any actions. The 'since' timestamp parameter is a filtering mechanism for queries, not an action trigger. Even though the server involves financial wagering (SOL tokens), this specific tool only reads results and does not move money or commit financial obligations.
From the tool's definition Tool description states 'Get your recent game and match results' and 'Returns both individual game results and spectator match competition results.' The verb 'Get' and 'Returns' indicate retrieval of historical data with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs razz_get_my_results 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_my_results, this is the rule to start with:
razz_get_my_results 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_my_results call is checked against it from then on.
Questions about razz_get_my_results
Get your recent game and match results. Use 'since' timestamp to only get new results since last check. Returns both individual game results and spectator match competition results. Ideal for cron-based agents that queue, disconnect, and check results later. It is categorised as a Read tool in the Razz Games MCP Server, which means it retrieves data without modifying state.
razz_get_my_results accepts 3 parameters: game, limit, since. 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_my_results: 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_my_results 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_my_results 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_my_results. 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_my_results 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