engine_move
A execute tool on the Chess MCP server.
This record as markdown: /tools/11hritik11-chess-mcp/engine-move.md
What engine_move does on Chess MCP Server
AI agents invoke engine_move to trigger actions in Chess MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why engine_move is rated High
Based on context from the server description (Stockfish engine, UCI format moves) and sibling tools, 'engine_move' likely triggers the Stockfish AI engine to calculate and make a move in a chess game. This constitutes an Execute action as it runs an external engine process and modifies game state. Confidence is lowered due to the empty description providing no direct evidence.
From the tool's definition Tool name 'engine_move' on a Chess MCP Server with sibling tools 'make_move' and 'new_game'. Description is empty.
Attacks that exploit this kind of access
The rule that runs engine_move safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Chess MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For engine_move, this is the rule to start with:
engine_move stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Chess MCP Server, apply this rule, and every engine_move call is checked against it from then on.
Questions about engine_move
engine_move is a execute tool on the Chess MCP Server MCP server. It is categorised as a Execute tool in the Chess MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Chess MCP Server MCP server in PolicyLayer and add a rule for engine_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 Chess MCP Server. Nothing to install.
engine_move is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the engine_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 engine_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.
engine_move is provided by the Chess MCP Server MCP server (11hritik11/chess-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Chess MCP Server, and thousands of servers like it.
Across the catalogue