validate_workflow_expressions
Validate all n8n expressions in a workflow. Checks: expression syntax ({{ }}), variable references ($json, $node, $input), node references exist, context availability. Returns specific errors with locations. Use this to catch expression errors before runtime.
This record as markdown: /tools/aegntic-aegntic-mcp/validate-workflow-expressions.md
What validate_workflow_expressions does on Obsidian Elite RAG MCP Server
AI agents invoke validate_workflow_expressions to trigger actions in Obsidian Elite RAG MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why validate_workflow_expressions is rated High
Validation tools that parse and evaluate expressions (even for correctness) are Execute-class because they run logic against supplied workflow content. The tool checks syntax and resolves variable/node references, meaning it actively processes and interprets expression code rather than merely reading static data. Misuse could expose internal workflow structure or be used to probe expression evaluation behavior.
From the tool's definition 'Validate all n8n expressions in a workflow' — triggers evaluation/parsing of workflow expressions including variable references and node context checks
Attacks that exploit this kind of access
The rule that runs validate_workflow_expressions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Obsidian Elite RAG MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For validate_workflow_expressions, this is the rule to start with:
validate_workflow_expressions stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Obsidian Elite RAG MCP Server, apply this rule, and every validate_workflow_expressions call is checked against it from then on.
Questions about validate_workflow_expressions
Validate all n8n expressions in a workflow. Checks: expression syntax ({{ }}), variable references ($json, $node, $input), node references exist, context availability. Returns specific errors with locations. Use this to catch expression errors before runtime. It is categorised as a Execute tool in the Obsidian Elite RAG MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Obsidian Elite RAG MCP Server MCP server in PolicyLayer and add a rule for validate_workflow_expressions: 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 Obsidian Elite RAG MCP Server. Nothing to install.
validate_workflow_expressions is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the validate_workflow_expressions 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 validate_workflow_expressions. 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.
validate_workflow_expressions is provided by the Obsidian Elite RAG MCP Server MCP server (aegntic/aegntic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Obsidian Elite RAG MCP Server, and thousands of servers like it.
Across the catalogue