AI agents call n8n_health_check 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 performs a diagnostic read-only operation. It retrieves health status and connectivity information about the n8n instance without creating, modifying, deleting, or executing any workflows or operations. The blast radius of misuse is minimal since health checks cannot cause damage to the system or data. This fits the 'Read' category as it queries and retrieves data with no side effects.
From the tool's definition The tool description states it 'Check[s] n8n instance health and API connectivity. Returns status and available features.' This is a query operation that retrieves health and status information with no modification, creation, or execution of workflows or data.
Attacks that exploit this kind of access
Check n8n instance health and API connectivity. Returns status and available features. 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 n8n_health_check: 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.
n8n_health_check 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 n8n_health_check 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 n8n_health_check. 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.
n8n_health_check 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 →