Get requirements for publishable levels
AI agents call get_level_requirements to retrieve information from Ice Puzzle without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries requirement information for publishing levels. It performs no side effects, creates no data, executes no code, and makes no modifications. It is purely informational, consistent with the Read category for tools that retrieve data without side effects.
From the tool's definition Tool name 'get_level_requirements' and description 'Get requirements for publishable levels' indicate a retrieval operation that queries or fetches existing requirements data without modifying any state.
Attacks that exploit this kind of access
Get requirements for publishable levels. It is categorised as a Read tool in the Ice Puzzle MCP Server, which means it retrieves data without modifying state.
Register the Ice Puzzle MCP server in PolicyLayer and add a rule for get_level_requirements: 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.
get_level_requirements is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_level_requirements 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 get_level_requirements. 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.
get_level_requirements 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 →