// SCAN REPORT

Pulse Workflow MCP Server

36 tools. 14 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 3 Jul 2026

14 can modify or destroy data

22 read-only

36 tools total

Community server · catalogue entry verified 03/07/2026

How to control Pulse Workflow MCP Server ↓

TOOL MAP

What Pulse Workflow MCP Server exposes to your agents

Read (22) Write / Execute (12) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Pulse Workflow MCP Server tools

Destructive · High delete_node This tool irreversibly removes data (nodes and their edges) from a workflow. Destructive · High delete_note The tool deletes a sticky note from a Pulse workflow, which is an irreversible action that cannot be undone. Execute · High run_node This tool triggers the execution of a workflow node, which constitutes code/operation execution. Write · Medium batch_add_nodes The tool creates (adds) multiple nodes within a Pulse workflow, which is a reversible modification.

14 of Pulse Workflow MCP Server's 36 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Pulse Workflow MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Pulse Workflow MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_node": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "add_node": {
    "limits": [
      {
        "counter": "add_node_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_agent_strategy": {
    "limits": [
      {
        "counter": "get_agent_strategy_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Pulse Workflow MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON PULSE WORKFLOW →

Instant setup, no code required.

FULL CATALOGUE

All 36 Pulse Workflow MCP Server tools

DESTRUCTIVE 2 tools

Destructive delete_node Delete node and its edges Destructive delete_note Delete sticky note

EXECUTE 1 tools

Execute run_node Execute single node for testing

WRITE 11 tools

Write add_node Add node. Returns: {node_id}. Use get_node_schema first for config format. Write add_note Add documentation note to canvas (visual only, not executed). Text supports newlines for paragraphs. Write batch_add_nodes Add multiple nodes at once. More efficient than multiple add_node calls. Write connect_nodes Create edge between nodes Write create_app Create app and auto-initialize workflow. Returns: {id, name, mode, start_node_id} Write disconnect_nodes Remove edge between nodes Write edit_node Update node (PATCH-style, only include changed fields) Write edit_note Update sticky note Write initialize_workflow Initialize workflow draft (auto-called by create_app) Write publish_workflow Publish draft as new version Write update_features Update features (partial)

READ 22 tools

Read get_agent_strategy Get agent strategy details including required parameters (instruction, query, model, tools, etc.) for agent_pa Read get_dataset Get dataset details Read get_document Get document details Read get_features Get workflow features config Read get_node Get node details Read get_node_schema REQUIRED before configuring a node. Get config schema for node type. Read get_variables Get environment and conversation variables Read list_agent_strategies List agent strategy providers for agent nodes. Returns providers with strategy names. Use get_agent_strategy f Read list_apps List apps. Returns: [{id, name, mode}] Read list_datasets List knowledge bases for RAG Read list_documents List documents in dataset Read list_edges List edges. Returns: [{id, source, target}] Read list_models List AI models for LLM nodes. Returns: [{provider, model, model_type}] Read list_node_types REQUIRED before add_node. Lists available node types. Read list_nodes List nodes. Returns: [{id, type, title}] Read list_notes List sticky notes Read list_tool_providers List external tool providers Read list_tools List tools from a provider with full schemas for agent configuration. Returns tool names, parameters (with for Read search_dataset Query knowledge base (hit testing). Returns: [{score, content, document_name}] Read select_app Select app for subsequent operations Read validate_workflow Check for errors. Returns: {valid, errors[], warnings[]} Read view_workflow View workflow structure. Returns: {nodes:[{id,type,title}], edges:[{source,target}]}

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Pulse Workflow MCP Server

Can an AI agent delete data through the Pulse Workflow MCP Server MCP server? +

Yes. The Pulse Workflow MCP Server server exposes 2 destructive tools including delete_node, delete_note. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Pulse Workflow MCP Server? +

The Pulse Workflow MCP Server server has 11 write tools including add_node, add_note, batch_add_nodes. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Pulse Workflow MCP Server.

How many tools does the Pulse Workflow MCP Server MCP server expose? +

36 tools across 4 categories: Destructive, Execute, Read, Write. 22 are read-only. 14 can modify, create, or delete data.

How do I enforce a policy on Pulse Workflow MCP Server? +

Register the Pulse Workflow MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Pulse Workflow MCP Server tool call.

Deterministic rules across all 36 Pulse Workflow MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON PULSE WORKFLOW →

Instant setup, no code required.

36 Pulse Workflow MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.