AI agents call get_node_subtree_stats to retrieve information from Dynalist without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Getting statistics about a subtree is a read-only operation that retrieves computed information without modifying, deleting, or executing arbitrary code. The minimal blast radius if misused (information disclosure only) supports 'low' severity.
From the tool's definition Tool name 'get_node_subtree_stats' and context indicate retrieval of statistics about document structure. Sibling tools include clear read operations (list_documents, get_recent_changes) and write operations (create_document, edit_items, delete_items),…
Attacks that exploit this kind of access
${INSTRUCTIONS_FIRST_GUIDANCE}. It is categorised as a Read tool in the Dynalist MCP Server, which means it retrieves data without modifying state.
Register the Dynalist MCP server in PolicyLayer and add a rule for get_node_subtree_stats: 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 Dynalist. Nothing to install.
get_node_subtree_stats 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 get_node_subtree_stats 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 get_node_subtree_stats. 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.
get_node_subtree_stats is provided by the Dynalist MCP server (wawworld/dynalist-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 →