# engine_move

A execute tool on the Chess MCP Server MCP server.

Agent View of the PolicyLayer registry record for `engine_move`. HTML page: https://policylayer.com/tools/11hritik11-chess-mcp/engine-move

## Facts

- Tool: `engine_move`
- Server: Chess MCP Server (`11hritik11/chess-mcp`) — https://policylayer.com/tools/11hritik11-chess-mcp.md
- Homepage: https://github.com/11hritik11/chess-mcp
- Risk category: Execute (High risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "engine_move",
    "arguments": {}
  }
}
```

## 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 own definition: "Tool name 'engine_move' on a Chess MCP Server with sibling tools 'make_move' and 'new_game'. Description is empty."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Chess MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "engine_move": {
      "limits": [
        {
          "counter": "engine_move_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Chess MCP Server (2)

- `new_game` — Execute — https://policylayer.com/tools/11hritik11-chess-mcp/new-game.md
- `make_move` — Write — https://policylayer.com/tools/11hritik11-chess-mcp/make-move.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=11hritik11-chess-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/11hritik11-chess-mcp