detect_quality_drift

📊 Detect data quality degradation: empty values, format violations, completeness issues. Identifies when data quality is declining.

Server n8n Workflow Builder schimmilab/n8n-workflow-builder
Category Read
Risk class Low
Parameters 00 required

What detect_quality_drift does on n8n Workflow Builder

AI agents call detect_quality_drift 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.

Why detect_quality_drift needs a policy

This is a monitoring and analysis tool that reads workflow data and metrics to report on quality issues. It has no side effects—it does not modify workflows, delete data, execute operations, or create financial obligations. The low severity reflects that misuse would only result in false alerts or missed quality issues, with no destructive or operational impact.

From the tool's definition Tool performs detection and analysis of data quality metrics ('Detect data quality degradation: empty values, format violations, completeness issues').

Questions about detect_quality_drift

What does the detect_quality_drift tool do? +

📊 Detect data quality degradation: empty values, format violations, completeness issues. Identifies when data quality is declining. It is categorised as a Read tool in the n8n Workflow Builder MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on detect_quality_drift? +

Register the n8n Workflow Builder MCP server in PolicyLayer and add a rule for detect_quality_drift: 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.

What risk level is detect_quality_drift? +

detect_quality_drift is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit detect_quality_drift? +

Yes. Add a rate_limit block to the detect_quality_drift 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.

How do I block detect_quality_drift completely? +

Set action: deny in the PolicyLayer policy for detect_quality_drift. 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.

What MCP server provides detect_quality_drift? +

detect_quality_drift 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.