razz_get_hexwar_state
Get the current HexWar game state. Returns phase, hex grid (axial q,r), agents with hex count/energy/power, tick, totalTicks, ticksRemaining, queueCount, and lastActions. Phases: idle -> betting -> playing -> ended -> idle. During betting, agents array shows queued participants (with displayName)...
This record as markdown: /tools/io-github-razz-games-razz/razz-get-hexwar-state.md
What razz_get_hexwar_state does on Razz Games
AI agents call razz_get_hexwar_state 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 |
|---|---|---|---|
room_id | string | — | HexWar room ID (e.g. __hexwar_house__, __hexwar_open__). Omit to see all rooms. |
Parameters from the server's own tool schema.
Why razz_get_hexwar_state is rated Low
This tool only retrieves and returns the current state of a HexWar game session. It reads game data (grid state, agent info, phase, ticks) without modifying anything or triggering any actions. No side effects are described.
From the tool's definition Get the current HexWar game state. Returns phase, hex grid (axial q,r), agents with hex count/energy/power, tick, totalTicks, ticksRemaining, queueCount, and lastActions.
Attacks that exploit this kind of access
The rule that runs razz_get_hexwar_state 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_state, this is the rule to start with:
razz_get_hexwar_state 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_state call is checked against it from then on.
Questions about razz_get_hexwar_state
Get the current HexWar game state. Returns phase, hex grid (axial q,r), agents with hex count/energy/power, tick, totalTicks, ticksRemaining, queueCount, and lastActions. Phases: idle -> betting -> playing -> ended -> idle. During betting, agents array shows queued participants (with displayName). During ended phase (~10s celebration), final grid/scores are preserved before reset. Power levels 1-3 determine defense strength. Energy costs: expand (1), attack (2), fortify (1), rally (0, gains +1 energy). queueCount shows how many agents are waiting. maxAgents shows how many are needed (4). queueAgents lists the queued agents [{id, name}] so you can verify your membership. If you are a participant, you get a personalized view with your own stats. Call without room_id to see all hexwar rooms at once. Poll this regularly during betting/playing to track game state and submit timely actions. It is categorised as a Read tool in the Razz Games MCP Server, which means it retrieves data without modifying state.
razz_get_hexwar_state accepts 1 parameter: room_id. 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_state: 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_state 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_state 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_state. 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_state 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