AI agents call get_node_as_tool_info 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 is a read-only documentation tool that returns metadata about n8n nodes and their usage patterns. It retrieves and presents information to help understand node functionality, equivalent to a search or information lookup operation. There is no execution of workflows, creation/modification of data, deletion, or financial impact.
From the tool's definition Tool provides informational guidance on 'how to use ANY node as AI tool' through 'requirements, use cases, examples' — retrieval and documentation of node capabilities with no side effects or data modification.
Attacks that exploit this kind of access
How to use ANY node as AI tool. Shows requirements, use cases, examples. Works for all nodes, not just AI-marked ones. 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_as_tool_info: 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_as_tool_info 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_as_tool_info 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_as_tool_info. 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_as_tool_info 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 →