comfyui.submit_flux_photoreal_pass

Submit a Flux-style photoreal workflow graph with project metadata

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cowork-os/comfyui.submit-flux-photoreal-pass.md

What comfyui.submit_flux_photoreal_pass does on CoWork OS

AI agents invoke comfyui.submit_flux_photoreal_pass to trigger actions in CoWork OS. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why comfyui.submit_flux_photoreal_pass is rated High

This tool submits a workflow graph to ComfyUI for execution, which runs an external AI image generation pipeline. It triggers computational operations whose effects depend on the provided arguments (workflow graph and project metadata).

From the tool's definition 'Submit a Flux-style photoreal workflow graph' — submits/executes a workflow graph, triggering external ComfyUI processing operations

Questions about comfyui.submit_flux_photoreal_pass

What does the comfyui.submit_flux_photoreal_pass tool do? +

Submit a Flux-style photoreal workflow graph with project metadata. It is categorised as a Execute tool in the CoWork OS MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

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

Register the CoWork OS MCP server in PolicyLayer and add a rule for comfyui.submit_flux_photoreal_pass: 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.submit_flux_photoreal_pass? +

comfyui.submit_flux_photoreal_pass is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit comfyui.submit_flux_photoreal_pass? +

Yes. Add a rate_limit block to the comfyui.submit_flux_photoreal_pass 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.submit_flux_photoreal_pass completely? +

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

comfyui.submit_flux_photoreal_pass 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of CoWork OS's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.