AI agents call get_database_statistics 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 queries and retrieves metadata statistics about the n8n node database. It performs a read-only inspection to verify system status and provide informational data. There are no side effects, no data modification, no code execution, and no destructive operations. The primary purpose is diagnostics and information retrieval, which clearly maps to the Read category.
From the tool's definition Tool retrieves and reports statistics about n8n nodes and documentation coverage. Description indicates it 'verifies MCP working' through data inspection with no modification, deletion, or execution capabilities mentioned.
Attacks that exploit this kind of access
Node stats: 525 total, 263 AI tools, 104 triggers, 87% docs coverage. Verifies MCP working. 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_database_statistics: 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_database_statistics 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_database_statistics 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_database_statistics. 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_database_statistics 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 →