AI agents call workflowy_get_node to retrieve information from WorkFlowy MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that retrieves information from WorkFlowy without creating, modifying, deleting, or executing actions. The blast radius of misuse is minimal — an attacker could only view existing node data they may not have authorization to see, which is a confidentiality concern but not destructive, irreversible, or operationally hazardous.
From the tool's definition Tool name contains 'get' and description states 'Retrieve a specific WorkFlowy node by ID' — both indicate data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access workflowy_get_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_get_node:
{
"version": "1",
"default": "deny",
"tools": {
"workflowy_get_node": {}
}
}workflowy_get_node is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieve a specific WorkFlowy node by ID. It is categorised as a Read tool in the WorkFlowy MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WorkFlowy MCP Server MCP server in PolicyLayer and add a rule for workflowy_get_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_get_node is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the workflowy_get_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_get_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_get_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.