evaluate_workflow_result · N8n Workflow Tester Safe MCP

WHAT IT DOES

What evaluate_workflow_result does on N8n Workflow Tester Safe

AI agents invoke evaluate_workflow_result to trigger actions in N8n Workflow Tester Safe. 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 IT NEEDS A POLICY

Why evaluate_workflow_result needs a policy

This tool executes workflows with user-supplied payloads and evaluates their outcomes. While scoped to 'testing' and 'scoring' (suggesting a safe context), it still executes arbitrary workflow logic whose side effects depend on the input payload.

From the tool's definition Tool 'evaluate_workflow_result' performs a 'test' action that 'runs' a payload and returns scoring/evaluation results. The description uses action words indicating execution: 'run', 'test', 'evaluate'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

evaluate_workflow_result Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "evaluate_workflow_result": {
      "limits": [
        {
          "counter": "evaluate_workflow_result_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches N8n Workflow Tester Safe, so you can run agents against it safely.

FAQ

Questions about evaluate_workflow_result

What does the evaluate_workflow_result tool do? +

Run a single payload test and return evaluation score + issues. It is categorised as a Execute tool in the N8n Workflow Tester Safe MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on evaluate_workflow_result? +

Register the N8n Workflow Tester Safe MCP server in PolicyLayer and add a rule for evaluate_workflow_result: 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 Tester Safe. Nothing to install.

What risk level is evaluate_workflow_result? +

evaluate_workflow_result is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit evaluate_workflow_result? +

Yes. Add a rate_limit block to the evaluate_workflow_result 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 evaluate_workflow_result completely? +

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

evaluate_workflow_result is provided by the N8n Workflow Tester Safe MCP server (souzix76/n8n-workflow-tester-safe). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.