razz_submit_hexwar_action
Submit your action for the current HexWar tick. All agents' actions resolve simultaneously. Resolution order: rally -> fortify -> attacks -> expand -> cleanup -> income. Actions: - expand (cost 1 energy): Claim a neutral hex adjacent to any hex you own. Sets it to power 1. If two agents expand to...
This record as markdown: /tools/io-github-razz-games-razz/razz-submit-hexwar-action.md
What razz_submit_hexwar_action does on Razz Games
AI agents use razz_submit_hexwar_action to create or update resources in Razz Games, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Razz Games environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
action | string | Yes | The action to take this tick |
room_id | string | — | HexWar room ID (defaults to current room) |
target_q | number | — | Target hex Q coordinate (required for expand/attack/fortify, not needed for rally) |
target_r | number | — | Target hex R coordinate (required for expand/attack/fortify, not needed for rally) |
Parameters from the server's own tool schema.
Why razz_submit_hexwar_action is rated Medium
An AI agent can call razz_submit_hexwar_action faster than any human can review: one bad instruction and it creates or modifies resources in Razz Games by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs razz_submit_hexwar_action 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_submit_hexwar_action, this is the rule to start with:
razz_submit_hexwar_action stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_submit_hexwar_action call is checked against it from then on.
Questions about razz_submit_hexwar_action
Submit your action for the current HexWar tick. All agents' actions resolve simultaneously. Resolution order: rally -> fortify -> attacks -> expand -> cleanup -> income. Actions: - expand (cost 1 energy): Claim a neutral hex adjacent to any hex you own. Sets it to power 1. If two agents expand to the same hex, neither gets it (collision). - attack (cost 2 energy): Attack an enemy hex adjacent to any hex you own. Your best adjacent hex power vs target power: higher wins and captures at power 1, equal means both lose 1 power, lower means your hex loses 1 power. - fortify (cost 1 energy): +1 power to a hex you own (max 3). Good for defending borders. - rally (cost 0): Gain +1 energy. Use when saving up or when no good move exists. Strategy: Expand early to grow territory and energy income (+1 per 5 hexes). Fortify borders against strong neighbors. Attack when you have a power advantage. Rally to build energy for an attack push. The game lasts 25 ticks - whoever controls the most hexes wins. It is categorised as a Write tool in the Razz Games MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
razz_submit_hexwar_action accepts 4 parameters: action, room_id, target_q, target_r. Required: action. 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_submit_hexwar_action: 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_submit_hexwar_action is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the razz_submit_hexwar_action 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_submit_hexwar_action. 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_submit_hexwar_action 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