List your marketplace levels with status filter, sorting, and pagination
AI agents call list_my_published_levels 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 queries and retrieves information about the user's published levels without modifying, executing, or deleting any data. It has no side effects beyond returning filtered results. The blast radius of misuse is minimal—an agent could only enumerate levels the user already owns, not alter game state, execute code, or cause financial impact.
From the tool's definition Tool name 'list_my_published_levels' and description 'List your marketplace levels with status filter, sorting, and pagination' indicate data retrieval operations only.
Attacks that exploit this kind of access
List your marketplace levels with status filter, sorting, and pagination. 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 list_my_published_levels: 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.
list_my_published_levels 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 list_my_published_levels 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 list_my_published_levels. 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.
list_my_published_levels 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 →