Place a tile (rock, lava, hot_coals, or spike) at position. Auto-solves.
AI agents use place_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 creates or modifies level data by placing tiles, which aligns with the Write category (creates or modifies data reversibly). While it may trigger some validation/solving logic, the core function is constructive modification of a puzzle level, not deletion, code execution, or financial operations.
From the tool's definition Tool description states it will 'Place a tile' at a position, which creates or modifies level data. The mention of 'Auto-solves' indicates it triggers computation but the primary action is creating/modifying game state (adding tiles to the level design).
Attacks that exploit this kind of access
Place a tile (rock, lava, hot_coals, or spike) at position. 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 place_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.
place_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 place_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 place_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.
place_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 →