batch_add_nodes · Pulse Workflow MCP Server MCP

WHAT IT DOES

What batch_add_nodes does on Pulse Workflow MCP Server

AI agents use batch_add_nodes to create or update resources in Pulse Workflow MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pulse Workflow MCP Server environment.

WHY IT NEEDS A POLICY

Why batch_add_nodes needs a policy

The tool creates (adds) multiple nodes within a Pulse workflow, which is a reversible modification. This qualifies as Write rather than Execute because it doesn't run arbitrary code or trigger external operations—it modifies workflow structure.

From the tool's definition Tool name 'batch_add_nodes' and description 'Add multiple nodes at once' indicate creation of multiple workflow elements. The description emphasizes efficiency over add_node calls, confirming this is a creation operation.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

batch_add_nodes Rate-limited

batch_add_nodes 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "batch_add_nodes": {
      "limits": [
        {
          "counter": "batch_add_nodes_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Pulse Workflow MCP Server, so you can run agents against it safely.

FAQ

Questions about batch_add_nodes

What does the batch_add_nodes tool do? +

Add multiple nodes at once. More efficient than multiple add_node calls. It is categorised as a Write tool in the Pulse Workflow MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on batch_add_nodes? +

Register the Pulse Workflow MCP Server MCP server in PolicyLayer and add a rule for batch_add_nodes: 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 Pulse Workflow MCP Server. Nothing to install.

What risk level is batch_add_nodes? +

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

Can I rate-limit batch_add_nodes? +

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

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

batch_add_nodes is provided by the Pulse Workflow MCP Server MCP server (pulse-intelligence/pulse-workflow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.