Get current n8n host and whether API key is configured
AI agents call get_n8n_status 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.
This tool retrieves status information about the N8N instance and API configuration state. It performs a read-only query with no capability to modify, delete, execute operations, or commit financial transactions. The low severity reflects that discovering the host and API key configuration status poses minimal risk—it is informational only and would not enable unauthorized actions by itself.
From the tool's definition Tool name 'get_n8n_status' and description 'Get current n8n host and whether API key is configured' indicates retrieval of status/configuration information with no side effects.
Attacks that exploit this kind of access
Get current n8n host and whether API key is configured. 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 get_n8n_status: 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.
get_n8n_status 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_n8n_status 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_n8n_status. 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_n8n_status 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 →