AI agents call nodes_list to retrieve information from Voog without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays metadata about page structure (id, title, parent_id, position) without creating, modifying, deleting, or executing any operations. It is a straightforward read-only query of the CMS hierarchy.
From the tool's definition Tool name is 'nodes_list' and description states 'List all page nodes' — a pure retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List all page nodes (id, title, parent_id, position). It is categorised as a Read tool in the Voog MCP Server, which means it retrieves data without modifying state.
Register the Voog MCP server in PolicyLayer and add a rule for nodes_list: 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 Voog. Nothing to install.
nodes_list 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 nodes_list 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 nodes_list. 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.
nodes_list is provided by the Voog MCP server (runnel/voog-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →