Say hello
AI agents call hello to retrieve information from N8N MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a basic greeting operation that has no capability to read sensitive data, modify state, execute code, delete resources, or trigger financial transactions. It is the least risky type of tool and serves only to verify connectivity or provide a friendly response. Classification as Read reflects that it may retrieve a static greeting message.
From the tool's definition Tool name is 'hello' with description 'Say hello'. This is a greeting/informational function that retrieves or returns a simple message with no side effects, data mutations, or external operations.
Attacks that exploit this kind of access
Say hello. It is categorised as a Read tool in the N8N MCP Server MCP Server, which means it retrieves data without modifying state.
Register the N8N MCP Server MCP server in PolicyLayer and add a rule for hello: 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 Server. Nothing to install.
hello 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 hello 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 hello. 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.
hello is provided by the N8N MCP Server MCP server (rajtrafficradius/n8n-mcpv2). 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 →