disconnect_nodes · Pulse Workflow MCP Server MCP

WHAT IT DOES

What disconnect_nodes does on Pulse Workflow MCP Server

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

The tool modifies a Pulse workflow by removing a connection between nodes. This is a Write operation because it creates or modifies data reversibly—the disconnection can be undone by reconnecting the nodes. It is not Read (no retrieval), Destructive (the workflow and nodes persist; only the edge is removed), Execute (does not run code or trigger external operations), Financial (no money involved), or Other.

From the tool's definition The tool removes an edge between nodes in a workflow, described as 'Remove edge between nodes'. This is a modification to the workflow structure that is reversible (the edge can be reconnected).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

disconnect_nodes Rate-limited

disconnect_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": {
    "disconnect_nodes": {
      "limits": [
        {
          "counter": "disconnect_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 disconnect_nodes

What does the disconnect_nodes tool do? +

Remove edge between nodes. 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 disconnect_nodes? +

Register the Pulse Workflow MCP Server MCP server in PolicyLayer and add a rule for disconnect_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 disconnect_nodes? +

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

Can I rate-limit disconnect_nodes? +

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

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

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