// SCAN REPORT

WorkFlowy MCP Server

7 tools. 5 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 12 Jun 2026

5 can modify or destroy data

2 read-only

7 tools total

Community server · catalogue entry verified 12/06/2026

How to control WorkFlowy MCP Server ↓

TOOL MAP

What WorkFlowy MCP Server exposes to your agents

Read (2) Write / Execute (4) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous WorkFlowy MCP Server tools

Destructive · High workflowy_delete_node This tool permanently removes data without the ability to undo the operation. Write · Medium workflowy_complete_node This tool modifies data state (task completion status) but the change is reversible—a completed node can be uncompleted. Write · Medium workflowy_create_node This tool creates new data structures (nodes) in the WorkFlowy system. Write · Medium workflowy_uncomplete_node The tool changes the completion status of a task/node from completed to incomplete.

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

POLICY

How to control WorkFlowy MCP Server

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

Deny destructive operations

{
  "workflowy_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

{
  "workflowy_complete_node": {
    "limits": [
      {
        "counter": "workflowy_complete_node_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "workflowy_get_node": {
    "limits": [
      {
        "counter": "workflowy_get_node_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 WorkFlowy 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 WORKFLOWY →

Free to start. No card required.

FULL CATALOGUE

All 7 WorkFlowy MCP Server tools

DESTRUCTIVE 1 tools

Destructive workflowy_delete_node Delete a WorkFlowy node and all its children

WRITE 4 tools

Write workflowy_complete_node Mark a WorkFlowy node as completed Write workflowy_create_node Create a new node in WorkFlowy Write workflowy_uncomplete_node Mark a WorkFlowy node as not completed Write workflowy_update_node Update an existing WorkFlowy node

READ 2 tools

Read workflowy_get_node Retrieve a specific WorkFlowy node by ID Read workflowy_list_nodes List WorkFlowy nodes (omit parent_id for root)

EXPLORE

Related servers

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

FAQ

Questions about WorkFlowy MCP Server

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

Yes. The WorkFlowy MCP Server server exposes 1 destructive tools including workflowy_delete_node. 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 WorkFlowy MCP Server? +

The WorkFlowy MCP Server server has 4 write tools including workflowy_complete_node, workflowy_create_node, workflowy_uncomplete_node. 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 WorkFlowy MCP Server.

How many tools does the WorkFlowy MCP Server MCP server expose? +

7 tools across 3 categories: Destructive, Read, Write. 2 are read-only. 5 can modify, create, or delete data.

How do I enforce a policy on WorkFlowy MCP Server? +

Register the WorkFlowy 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 WorkFlowy MCP Server tool call.

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

ENFORCE POLICY ON WORKFLOWY →

Free to start. No card required.

7 WorkFlowy MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.