📋 Detect API schema changes: missing fields, type changes, structure changes. Identifies breaking API changes before they cause failures.
AI agents call detect_schema_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.
This tool reads and analyzes API schema metadata to identify differences and potential issues. It performs no mutations, executions, or destructive operations. The output is informational analysis intended to prevent downstream failures, making it a Read category tool with low severity—the worst case is incomplete or incorrect schema analysis, which does not directly impact systems.
From the tool's definition Tool performs schema detection and analysis to identify 'missing fields, type changes, structure changes' and 'breaking API changes'.
Attacks that exploit this kind of access
📋 Detect API schema changes: missing fields, type changes, structure changes. Identifies breaking API changes before they cause failures. 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 detect_schema_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.
detect_schema_drift 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 detect_schema_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.
Set action: deny in the PolicyLayer policy for detect_schema_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.
detect_schema_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.
detect_schema_drift is one line of n8n Workflow Builder's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →