validate_workflow · Respan MCP Server MCP: Risk & Policy

WHAT IT DOES

What validate_workflow does on Respan MCP Server

AI agents invoke validate_workflow to trigger actions in Respan 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 IT NEEDS A POLICY

Why validate_workflow needs a policy

Despite being named 'validate', this tool executes a workflow against sample data. Running a workflow constitutes an Execute-category action because its effects depend on the workflow's logic and arguments. The blast radius is medium since it runs against a sample log (likely sandboxed), but execution of arbitrary workflow logic could have unintended side effects.

From the tool's definition 'Validate a workflow by running it against a sample log' — the tool actively runs/executes a workflow, not merely reads or inspects it.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

validate_workflow Rate-limited

validate_workflow 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": {
    "validate_workflow": {
      "limits": [
        {
          "counter": "validate_workflow_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 Respan MCP Server, so you can run agents against it safely.

FAQ

Questions about validate_workflow

What does the validate_workflow tool do? +

Validate a workflow by running it against a sample log. Returns validation results and any errors. It is categorised as a Execute tool in the Respan MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on validate_workflow? +

Register the Respan MCP Server MCP server in PolicyLayer and add a rule for validate_workflow: 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 Respan MCP Server. Nothing to install.

What risk level is validate_workflow? +

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

Can I rate-limit validate_workflow? +

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

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

validate_workflow is provided by the Respan MCP Server MCP server (respanai/respan-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.