High Risk →

wait_for_job

Wait for a job to complete. Polls the job status until it finishes or timeout is reached.

Part of the Comfyui Mcp Server Node MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

comfyui-mcp-server-node Execute Risk 3/5

AI agents invoke wait_for_job to trigger processes or run actions in Comfyui Mcp Server Node. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

wait_for_job can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

comfyui-mcp-server-node.yaml
tools:
  wait_for_job:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Comfyui Mcp Server Node policy for all 15 tools.

Tool Name wait_for_job
Category Execute
Risk Level High

View all 15 tools →

Agents calling execute-class tools like wait_for_job have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

wait_for_job is one of the high-risk operations in Comfyui Mcp Server Node. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the wait_for_job tool do? +

Wait for a job to complete. Polls the job status until it finishes or timeout is reached.. It is categorised as a Execute tool in the Comfyui Mcp Server Node MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on wait_for_job? +

Add a rule in your Intercept YAML policy under the tools section for wait_for_job. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Comfyui Mcp Server Node MCP server.

What risk level is wait_for_job? +

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

Can I rate-limit wait_for_job? +

Yes. Add a rate_limit block to the wait_for_job rule in your Intercept 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 wait_for_job completely? +

Set action: deny in the Intercept policy for wait_for_job. 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 wait_for_job? +

wait_for_job is provided by the Comfyui Mcp Server Node MCP server (comfyui-mcp-server-node). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Comfyui Mcp Server Node

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.