Update tags for a workflow
AI agents use n8n_update_workflow_tags to create or update resources in n8n MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your n8n MCP Server environment.
Updating tags is a reversible modification operation that changes workflow metadata but does not execute workflows, delete data, or cause irreversible changes. It falls under Write category. Severity is medium because tag manipulation could affect workflow organization and filtering, potentially impacting visibility and access control in a multi-user n8n environment, but the impact is scoped to metadata only.
From the tool's definition Tool name includes 'update' and description states 'Update tags for a workflow' — this modifies workflow metadata reversibly.
Attacks that exploit this kind of access
Update tags for a workflow. It is categorised as a Write tool in the n8n MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the n8n MCP Server MCP server in PolicyLayer and add a rule for n8n_update_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_update_workflow_tags is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the n8n_update_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_update_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_update_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 →