Add thin ice tiles (break after crossing)
AI agents use add_thin_ice 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 adds game elements (thin ice tiles) to an Ice Puzzle level during the design phase. This is a Write operation because it creates or modifies game level data reversibly. The effects are limited to level design state and can be undone (evidenced by sibling tools like 'clear_level' and 'delete_draft').
From the tool's definition Tool name 'add_thin_ice' and description 'Add thin ice tiles (break after crossing)' indicate the tool creates or modifies level design elements.
Attacks that exploit this kind of access
Add thin ice tiles (break after crossing). 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 add_thin_ice: 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.
add_thin_ice 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 add_thin_ice 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 add_thin_ice. 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.
add_thin_ice 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 →