Medium Risk

add_node

Add a node to a dynamic workflow. Returns the new node id (e.g.

Part of the ComfyUI Builder server.

add_node can modify ComfyUI Builder data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE COMFYUI BUILDER →

Free to start. No card required.

AI agents use add_node to create or modify resources in ComfyUI Builder. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call add_node repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach ComfyUI Builder.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_node": {
      "limits": [
        {
          "counter": "add_node_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full ComfyUI Builder policy for all 60 tools.

Get this rule live on your own ComfyUI Builder server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY COMFYUI BUILDER →

View all 60 tools →

These attack patterns abuse exactly the kind of access add_node gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so add_node only ever does what you allow.

SECURE COMFYUI BUILDER →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the add_node tool do? +

Add a node to a dynamic workflow. Returns the new node id (e.g.. It is categorised as a Write tool in the ComfyUI Builder MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_node? +

Register the ComfyUI Builder MCP server in PolicyLayer and add a rule for add_node: 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 Builder. Nothing to install.

What risk level is add_node? +

add_node is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_node? +

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

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

add_node is provided by the ComfyUI Builder MCP server (mcp-comfy-ui-builder). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ComfyUI Builder tool call.

Deterministic rules across all 60 ComfyUI Builder tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.