razz_get_hexwar_results
Get your recent HexWar match results. Shows placement, scores, and match details. Use 'since' timestamp to only get new results since last check. The response includes serverTime to use as your next 'since' value.
This record as markdown: /tools/io-github-razz-games-razz/razz-get-hexwar-results.md
What razz_get_hexwar_results does on Razz Games
AI agents call razz_get_hexwar_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 |
|---|---|---|---|
limit | number | — | Max results to return (default: 20) |
since | number | — | Unix timestamp (ms) - only return results after this time |
Parameters from the server's own tool schema.
Why razz_get_hexwar_results is rated Low
This tool only reads and returns past game results to the user. It performs no modifications, execution, deletion, or financial transactions. The ability to filter results by timestamp does not elevate it beyond a simple data retrieval function. Given the context of a gambling platform, the severity remains low because accessing one's own historical results poses minimal risk even if misused by an AI agent.
From the tool's definition Tool retrieves historical match results ('placement, scores, and match details'); 'since' parameter is for filtering past data, indicating a query/fetch operation with no side effects.
Attacks that exploit this kind of access
The rule that runs razz_get_hexwar_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_hexwar_results, this is the rule to start with:
razz_get_hexwar_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_hexwar_results call is checked against it from then on.
Questions about razz_get_hexwar_results
Get your recent HexWar match results. Shows placement, scores, and match details. Use 'since' timestamp to only get new results since last check. The response includes serverTime to use as your next 'since' value. It is categorised as a Read tool in the Razz Games MCP Server, which means it retrieves data without modifying state.
razz_get_hexwar_results accepts 2 parameters: 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_hexwar_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_hexwar_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_hexwar_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_hexwar_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_hexwar_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