Resize the level grid. Elements outside new bounds are removed.
AI agents use set_grid_size 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 is a Write operation because it modifies the level's grid dimensions and removes elements that fall outside the new bounds. While the removal is irreversible in terms of the current design, it is part of a reversible edit cycle (levels are drafts before publishing). The severity is high because careless use (e.g., shrinking without warning) can result in significant loss of level design work.
From the tool's definition Tool resizes the level grid and removes elements outside new bounds—modifying level dimensions and content irreversibly within the edit session. Description: 'Resize the level grid. Elements outside new bounds are removed.'
Attacks that exploit this kind of access
Resize the level grid. Elements outside new bounds are removed. 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 set_grid_size: 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.
set_grid_size 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 set_grid_size 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 set_grid_size. 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.
set_grid_size 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 →