comfyui.get_history

Get ComfyUI history, optionally for one prompt id

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cowork-os/comfyui.get-history.md

WHAT IT DOES

What comfyui.get_history does on CoWork OS

AI agents call comfyui.get_history to retrieve information from CoWork OS without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why comfyui.get_history is rated Low

This tool retrieves or fetches historical information from ComfyUI (a local AI image generation tool) without modifying, executing, deleting, or creating any data. The optional filtering by prompt id does not change the fundamental read-only nature of the operation. No blast radius from misuse beyond potential information disclosure.

From the tool's definition Tool name and description indicate 'Get ComfyUI history' — a retrieval operation that queries historical data, optionally filtered by prompt id. The verb 'Get' combined with 'history' clearly denotes a read-only query with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs comfyui.get_history safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For comfyui.get_history, this is the rule to start with:

comfyui.get_history Allowed

comfyui.get_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "comfyui.get_history": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every comfyui.get_history call is checked against it from then on.

FAQ

Questions about comfyui.get_history

What does the comfyui.get_history tool do? +

Get ComfyUI history, optionally for one prompt id. It is categorised as a Read tool in the CoWork OS MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on comfyui.get_history? +

Register the CoWork OS MCP server in PolicyLayer and add a rule for comfyui.get_history: 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 CoWork OS. Nothing to install.

What risk level is comfyui.get_history? +

comfyui.get_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit comfyui.get_history? +

Yes. Add a rate_limit block to the comfyui.get_history 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.

How do I block comfyui.get_history completely? +

Set action: deny in the PolicyLayer policy for comfyui.get_history. 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.

What MCP server provides comfyui.get_history? +

comfyui.get_history is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →