comfyui.collect_outputs
Collect output image URLs for a completed prompt id and optionally copy them under the project root
This record as markdown: /tools/cowork-os/comfyui.collect-outputs.md
What comfyui.collect_outputs does on CoWork OS
AI agents use comfyui.collect_outputs to create or update resources in CoWork OS, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CoWork OS environment.
Why comfyui.collect_outputs is rated Medium
The primary action is collecting/retrieving output URLs (Read), but the optional 'copy' functionality creates or adds files to the project directory, making this a Write operation. The severity is medium because unintended file copies could clutter the project filesystem and consume storage, but the impact is reversible and localized.
From the tool's definition 'Collect output image URLs for a completed prompt id and optionally copy them under the project root' — the tool retrieves URLs but also performs 'copy them under the project root', which creates/modifies files on the filesystem.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs comfyui.collect_outputs 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.collect_outputs, this is the rule to start with:
comfyui.collect_outputs stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every comfyui.collect_outputs call is checked against it from then on.
Questions about comfyui.collect_outputs
Collect output image URLs for a completed prompt id and optionally copy them under the project root. It is categorised as a Write tool in the CoWork OS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CoWork OS MCP server in PolicyLayer and add a rule for comfyui.collect_outputs: 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.
comfyui.collect_outputs is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the comfyui.collect_outputs 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 comfyui.collect_outputs. 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.
comfyui.collect_outputs 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.
More on CoWork OS, and thousands of servers like it.
This server
Across the catalogue