🔬 Deep analysis of a specific drift pattern. Finds when drift started, whether it was gradual, and potential causes.
AI agents call analyze_drift_pattern to retrieve information from n8n Workflow Builder without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes existing workflow drift data to provide insights. It queries historical state information and patterns without making changes, triggering external operations, or causing side effects. The output is informational analysis used for understanding workflow deviations, consistent with Read category operations like search and fetch.
From the tool's definition Tool performs 'deep analysis' of drift patterns, examining timeline ('when drift started'), progression ('whether it was gradual'), and potential causes. The description uses only analytical verbs: analysis, finds, and examination.
Attacks that exploit this kind of access
🔬 Deep analysis of a specific drift pattern. Finds when drift started, whether it was gradual, and potential causes. It is categorised as a Read tool in the n8n Workflow Builder MCP Server, which means it retrieves data without modifying state.
Register the n8n Workflow Builder MCP server in PolicyLayer and add a rule for analyze_drift_pattern: 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 Workflow Builder. Nothing to install.
analyze_drift_pattern 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 analyze_drift_pattern 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 analyze_drift_pattern. 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.
analyze_drift_pattern is provided by the n8n Workflow Builder MCP server (schimmilab/n8n-workflow-builder). 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 →