Run BFS solver on current level with direction balance and unsolvable diagnostics
AI agents invoke solve_level 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.
This tool executes code (a breadth-first search algorithm) to analyze and return solver diagnostics about the current level. While not destructive or modifying persisted state directly, it triggers an external computational operation whose behavior depends on the level configuration. The side effects (generating solver feedback, diagnostics) are transient and reversible, placing it in Execute rather than Write.
From the tool's definition Tool performs an algorithmic operation ('Run BFS solver') on a game level state, executing a computational process with observable effects on solver analysis.
Attacks that exploit this kind of access
Run BFS solver on current level with direction balance and unsolvable diagnostics. 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.
Register the Ice Puzzle MCP server in PolicyLayer and add a rule for solve_level: 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.
solve_level is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the solve_level 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 solve_level. 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.
solve_level 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 →