AI agents invoke start 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.
Starting a server is an Execute operation as it runs/triggers an external operation whose effects depend on context (which server, what load, what state). While the effects are somewhat reversible (stopping the server), the primary action is an execution trigger. This is not Destructive since starting a service is not irreversible data deletion, but it does carry high severity due to potential operational impact.
From the tool's definition 'Start n8n server' is a command that initiates an external service/process, which is an operation that triggers system state changes and potentially affects availability and resource allocation.
Attacks that exploit this kind of access
Start n8n server - replaces. 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 start: 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.
start 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 start 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 start. 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.
start 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 →