AI agents call get_publish_info to retrieve information from ComfyUI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to query information about publishing configuration or status rather than execute publishing actions or modify data. Without description details, confidence is moderate, but the naming convention and context within a read-heavy tool suite point to a passive information retrieval function.
From the tool's definition Tool name 'get_publish_info' indicates a retrieval/query operation. The empty description reduces specificity, but the 'get_' prefix and comparison with sibling tools (get_asset_metadata, get_defaults, get_job, get_queue_status, list_assets, list_models,…
Documented attack patterns abuse exactly the kind of access get_publish_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ComfyUI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_publish_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_publish_info": {}
}
}get_publish_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_publish_info. It is categorised as a Read tool in the ComfyUI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ComfyUI MCP Server MCP server in PolicyLayer and add a rule for get_publish_info: 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 ComfyUI MCP Server. Nothing to install.
get_publish_info 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_publish_info 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_publish_info. 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_publish_info is provided by the ComfyUI MCP Server MCP server (joenorton/comfyui-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ComfyUI MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
15 ComfyUI MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.