AI agents invoke deploy to trigger actions in McFlow. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Deployment of workflows to a live n8n instance is an Execute operation because it triggers external operations (workflow execution, automation, integrations) whose effects depend on the arguments (workflow content). While not directly destructive or financial, misuse could cause unintended automation, data processing, or integration side effects in the connected n8n instance.
From the tool's definition Tool description states 'Deploy workflows to n8n instance - handles all n8n import commands internally'. The deploy action executes workflow deployment operations against an external n8n system, triggering automation logic whose effects depend on the workflow…
Attacks that exploit this kind of access
Deploy workflows to n8n instance - handles all n8n import commands internally. It is categorised as a Execute tool in the McFlow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the McFlow MCP server in PolicyLayer and add a rule for deploy: 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 McFlow. Nothing to install.
deploy is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the deploy 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 deploy. 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.
deploy is provided by the McFlow MCP server (mckinleymedia/mcflow-mcp). 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 →