AI agents call get_node_documentation to retrieve information from n8n-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries documentation about n8n nodes, making it a Read operation. It has no side effects on data, workflows, or external systems. Severity is low because documentation access poses minimal risk even if an AI agent misuses it; the worst outcome is obtaining incorrect or misleading information about node capabilities, not actual execution or data modification.
From the tool's definition Tool name 'get_node_documentation' and description indicate retrieval of documentation with examples, authentication info, and patterns. No mutation, deletion, or execution of workflows/operations occurs—purely informational lookup.
Attacks that exploit this kind of access
Get readable docs with examples/auth/patterns. Better than raw schema! 87% coverage. Format:. It is categorised as a Read tool in the n8n-MCP MCP Server, which means it retrieves data without modifying state.
Register the n8n- MCP server in PolicyLayer and add a rule for get_node_documentation: 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 n8n-MCP. Nothing to install.
get_node_documentation 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_documentation 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_documentation. 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_documentation is provided by the n8n- MCP server (mohsin-zaheer/mcp-server). 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 →