simulate_move · Ice Puzzle MCP: Risk & Policy

WHAT IT DOES

What simulate_move does on Ice Puzzle

AI agents invoke simulate_move to trigger actions in Ice Puzzle. 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 IT NEEDS A POLICY

Why simulate_move needs a policy

The tool executes a simulation of a game move, computing outcomes based on provided position and direction arguments. It does not read static stored data, write persistent data, or delete anything — it runs a dynamic computation whose result depends on arguments. Severity is low because it only simulates within a puzzle context with no external side effects.

From the tool's definition "Simulate a single slide move from a position" — runs a simulation/computation based on input arguments

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

simulate_move Rate-limited

simulate_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "simulate_move": {
      "limits": [
        {
          "counter": "simulate_move_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Ice Puzzle, so you can run agents against it safely.

FAQ

Questions about simulate_move

What does the simulate_move tool do? +

Simulate a single slide move from a position. It is categorised as a Execute tool in the Ice Puzzle MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on simulate_move? +

Register the Ice Puzzle MCP server in PolicyLayer and add a rule for simulate_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 Ice Puzzle. Nothing to install.

What risk level is simulate_move? +

simulate_move is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit simulate_move? +

Yes. Add a rate_limit block to the simulate_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.

How do I block simulate_move completely? +

Set action: deny in the PolicyLayer policy for simulate_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.

What MCP server provides simulate_move? +

simulate_move is provided by the Ice Puzzle MCP server (wmoten/ice-puzzle-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.