AI agents call n8n_get_workflow 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 retrieves and returns workflow data based on an ID parameter. It performs no modifications, deletions, or external operations. This is a straightforward Read operation with minimal security impact - the blast radius is limited to information disclosure of workflow configurations that an authorized user would have access to.
From the tool's definition Tool name and description both indicate retrieval functionality: "Get a workflow by ID" and "Returns the complete workflow". This is a query operation that retrieves existing data without modification or side effects.
Attacks that exploit this kind of access
Get a workflow by ID. Returns the complete workflow including nodes, connections, and settings. 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: 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 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 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. 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 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 →