🔍 Check workflow for node compatibility issues with current n8n version.
AI agents call check_workflow_compatibility 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 workflow compatibility status against the current n8n version. It performs checks and validation without creating, modifying, deleting, or executing any workflows or system operations. The action is informational and diagnostic, returning analysis results. No data is created, destroyed, or irreversibly changed. Classification as Read is appropriate.
From the tool's definition Tool is described as 'Check workflow for node compatibility issues' — the verb 'check' indicates inspection/analysis with no modifications or side effects. The 🔍 emoji reinforces a diagnostic/read-only purpose.
Attacks that exploit this kind of access
🔍 Check workflow for node compatibility issues with current n8n version. 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 check_workflow_compatibility: 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.
check_workflow_compatibility 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 check_workflow_compatibility 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 check_workflow_compatibility. 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.
check_workflow_compatibility 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 →