connect_nodes · Pulse Workflow MCP Server MCP: Risk & Policy

WHAT IT DOES

What connect_nodes does on Pulse Workflow MCP Server

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

This tool creates new edges (connections) in a workflow graph, which is a reversible data modification operation. It does not retrieve data (Read), execute arbitrary operations (Execute), delete data irreversibly (Destructive), or involve financial transactions (Financial). It falls squarely in the Write category.

From the tool's definition Tool name is 'connect_nodes' and description states 'Create edge between nodes'. The word 'Create' indicates this tool creates/modifies workflow structure by establishing connections between nodes in a Pulse workflow.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

connect_nodes Rate-limited

connect_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": {
    "connect_nodes": {
      "limits": [
        {
          "counter": "connect_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 connect_nodes

What does the connect_nodes tool do? +

Create 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 connect_nodes? +

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

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

Can I rate-limit connect_nodes? +

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

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

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