AI agents use make_move to create or update resources in MCP Chess Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Chess Server environment.
Based on the server context (chess game) and tool name, 'make_move' most likely updates the game state by recording a chess move. This is a reversible write operation (game state modification), not destructive. Confidence is reduced due to the empty description, but the chess context strongly implies a state-modifying write action with low blast radius.
From the tool's definition Tool name 'make_move' on a chess server; description is empty
Documented attack patterns abuse exactly the kind of access make_move gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Chess Server, and nothing reaches the server without passing your rules. This is the rule we recommend for make_move:
{
"version": "1",
"default": "deny",
"tools": {
"make_move": {
"limits": [
{
"counter": "make_move_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}make_move 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.
Free to start. No card required.
make_move. It is categorised as a Write tool in the MCP Chess Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Chess Server 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 MCP Chess Server. 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 MCP Chess Server MCP server (jiayao/mcp-chess). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Chess Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 MCP Chess Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.