AI agents use make_move to create or update resources in Gomoku — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gomoku environment.
This tool writes a game move to the board, modifying the game state. It is reversible in the sense that game state is just data, and there is no destructive, financial, or code-execution aspect. Blast radius is very low as it only affects a game session.
From the tool's definition 在指定位置下棋 (make a move at a specified position) — creates/modifies game state by placing a piece on the board
Attacks that exploit this kind of access
在指定位置下棋. It is categorised as a Write tool in the Gomoku MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gomoku MCP server in PolicyLayer and add a rule for make_move: 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 Gomoku. Nothing to install.
make_move 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 make_move 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 make_move. 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.
make_move is provided by the Gomoku MCP server (sanshao85/gomoku-ai-battle). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →