Check publish blockers: auth status + strict quality gate
AI agents call check_publish_readiness 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 validates state (authentication and quality criteria) but does not create, modify, delete, or execute external operations. It is purely informational, returning whether conditions are met for publishing. Therefore, it belongs in the Read category with low severity, as misuse would only expose validation status information without enabling destructive or financial actions.
From the tool's definition The tool "check_publish_readiness" performs validation checks ("auth status + strict quality gate") to assess whether a level is ready for publication.
Attacks that exploit this kind of access
Check publish blockers: auth status + strict quality gate. 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 check_publish_readiness: 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.
check_publish_readiness 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 check_publish_readiness 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 check_publish_readiness. 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.
check_publish_readiness 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 →