AI agents use workflowy_complete_node to create or update resources in WorkFlowy MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WorkFlowy MCP Server environment.
This tool modifies data state (task completion status) but the change is reversible—a completed node can be uncompleted. This qualifies as Write rather than Destructive. The severity is medium because marking tasks as complete could affect workflow and decision-making, but the impact is limited to task metadata and the action is undoable.
From the tool's definition The tool 'workflowy_complete_node' marks a node as completed, which modifies the state of a task/node in the WorkFlowy system. The description explicitly states it performs a state change ('Mark a WorkFlowy node as completed').
Documented attack patterns abuse exactly the kind of access workflowy_complete_node gives an agent:
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_complete_node:
{
"version": "1",
"default": "deny",
"tools": {
"workflowy_complete_node": {
"limits": [
{
"counter": "workflowy_complete_node_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}workflowy_complete_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.
Free to start. No card required.
Mark a WorkFlowy node as completed. 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.
Register the WorkFlowy MCP Server MCP server in PolicyLayer and add a rule for workflowy_complete_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.
workflowy_complete_node is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the workflowy_complete_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.
Set action: deny in the PolicyLayer policy for workflowy_complete_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.
workflowy_complete_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.
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.
Free to start. No card required.
7 WorkFlowy MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.