Move one tile/special element from one coordinate to another. Auto-solves.
AI agents use move_tile to create or update resources in Ice Puzzle — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ice Puzzle environment.
This tool modifies level data by moving tiles to new positions—a reversible change typical of level editing. It does not delete data (thus not Destructive), does not execute arbitrary code (thus not Execute), and does not involve financial transactions. The 'auto-solve' feature is a convenience mechanism, not the primary capability.
From the tool's definition Tool description states it 'Move[s] one tile/special element from one coordinate to another', which modifies level design state. The phrase 'Auto-solves' indicates it performs automatic solving, but the primary function is repositioning level elements.
Attacks that exploit this kind of access
Move one tile/special element from one coordinate to another. Auto-solves. It is categorised as a Write tool in the Ice Puzzle MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ice Puzzle MCP server in PolicyLayer and add a rule for move_tile: 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.
move_tile 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 move_tile 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 move_tile. 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.
move_tile 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.
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 →