AI agents call n8n_get_workflow_structure 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.
The tool only retrieves and queries workflow structural data (nodes and connections). It has no side effects, does not execute workflows, does not create or modify data, and is clearly informational in nature. This falls squarely within the Read category. Severity is low because an AI misusing this tool can only inspect existing workflow configurations without causing harm.
From the tool's definition Tool description states it 'Get[s] workflow structure: nodes and connections only. No parameter details.' This is a read-only operation that retrieves workflow information without executing, modifying, or deleting anything.
Attacks that exploit this kind of access
Get workflow structure: nodes and connections only. No parameter details. 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_get_workflow_structure: 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_get_workflow_structure 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_get_workflow_structure 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_get_workflow_structure. 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_get_workflow_structure 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 →