Get tags for a workflow
AI agents call n8n_get_workflow_tags 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 queries and retrieves metadata (tags) associated with a workflow. It is a read-only operation that does not create, modify, delete, execute code, or trigger external operations. The only risk is information disclosure, which is minimal for workflow tags. Severity is low because tags are typically non-sensitive metadata and their exposure does not compromise system integrity or data security.
From the tool's definition Tool name 'n8n_get_workflow_tags' and description 'Get tags for a workflow' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get tags for a workflow. 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 n8n_get_workflow_tags: 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.
n8n_get_workflow_tags 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_tags 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_tags. 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_tags is provided by the n8n MCP Server MCP server (shravan1610/n8n-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 →