add_node · Pulse Workflow MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_node does on Pulse Workflow MCP Server

AI agents use add_node 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 add_node needs a policy

Adding a node to a workflow is a reversible write operation—it creates new data (a workflow node) that can be undone via delete_node. It does not execute arbitrary code, delete data irreversibly, or move money. The severity is medium because workflow modification could affect automated processes, but the impact is scoped to the workflow design itself rather than external systems.

From the tool's definition Tool adds a node to a workflow, which creates new data structures within the workflow graph. Description states 'Add node' and returns a node_id, indicating creation of a new entity.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_node Rate-limited

add_node 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": {
    "add_node": {
      "limits": [
        {
          "counter": "add_node_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 add_node

What does the add_node tool do? +

Add node. Returns: {node_id}. Use get_node_schema first for config format. 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 add_node? +

Register the Pulse Workflow MCP Server 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 Pulse Workflow MCP Server. 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 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.