workflowy_create_node

THE RISK

Medium Risk

Why workflowy_create_node needs a policy

This tool creates new data structures (nodes) in the WorkFlowy system. Creation is a Write operation because nodes can be subsequently deleted or modified. Severity is medium because misuse could clutter or pollute the user's workspace with unwanted nodes, but the effect is reversible through deletion. Confidence is high given the explicit 'create' verb in both name and description.

From the tool's definition Tool name is 'workflowy_create_node' and description states 'Create a new node in WorkFlowy'. The verb 'create' indicates data creation, which is a reversible write operation.

Documented attack patterns abuse exactly the kind of access workflowy_create_node gives an agent:

POLICY

How to control workflowy_create_node

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "workflowy_create_node": {
      "limits": [
        {
          "counter": "workflowy_create_node_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

Create a free account and register WorkFlowy MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More WorkFlowy MCP Server tools

Destructive workflowy_delete_node Delete a WorkFlowy node and all its children Write workflowy_complete_node Mark a WorkFlowy node as completed Write workflowy_uncomplete_node Mark a WorkFlowy node as not completed Write workflowy_update_node Update an existing WorkFlowy node Read workflowy_get_node Retrieve a specific WorkFlowy node by ID Read workflowy_list_nodes List WorkFlowy nodes (omit parent_id for root)

All 7 WorkFlowy MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about workflowy_create_node

What does the workflowy_create_node tool do? +

Create a new node in WorkFlowy. It is categorised as a Write tool in the WorkFlowy 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 workflowy_create_node? +

Register the WorkFlowy MCP Server MCP server in PolicyLayer and add a rule for workflowy_create_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 WorkFlowy MCP Server. Nothing to install.

What risk level is workflowy_create_node? +

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

Can I rate-limit workflowy_create_node? +

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

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

workflowy_create_node is provided by the WorkFlowy MCP Server MCP server (vladzima/workflowy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every WorkFlowy MCP Server tool call.

Start from WorkFlowy MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →