Get one of your published marketplace levels by ID
AI agents call get_my_published_level 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 a single published level from the marketplace by its ID. The verb 'get' and the context of querying existing published data (not creating, modifying, or deleting) clearly classify this as a Read operation. The severity is low because retrieval of public or user-owned published content poses minimal risk—there are no side effects, state changes, or irreversible actions.
From the tool's definition Tool name 'get_my_published_level' and description 'Get one of your published marketplace levels by ID' indicate retrieval of existing published data with no modification or deletion.
Attacks that exploit this kind of access
Get one of your published marketplace levels by ID. 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_my_published_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.
get_my_published_level 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_my_published_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 get_my_published_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.
get_my_published_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 →