🎯 Determine root cause of detected drift. Analyzes patterns and provides evidence-based root cause with confidence score.
AI agents call get_drift_root_cause 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 reads workflow state data and existing drift analysis results to determine root causes, returning analytical insights. It has no side effects, does not execute workflows or code, does not modify data, and does not delete or move resources. The capability to analyze and report findings is consistent with Read category tools that support debugging and monitoring without changing system state.
From the tool's definition Tool name 'get_drift_root_cause' and description 'Analyzes patterns and provides evidence-based root cause with confidence score' indicate data retrieval and analysis only. No modification, execution, deletion, or financial operations are performed.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
🎯 Determine root cause of detected drift. Analyzes patterns and provides evidence-based root cause with confidence score. 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 get_drift_root_cause: 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.
get_drift_root_cause 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 get_drift_root_cause 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 get_drift_root_cause. 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.
get_drift_root_cause 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 →