veritas_run_pipeline · Mcp-Omega-Brain MCP: Risk & Policy

WHAT IT DOES

What veritas_run_pipeline does on Mcp-Omega-Brain

AI agents invoke veritas_run_pipeline to trigger actions in Mcp-Omega-Brain. 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 veritas_run_pipeline needs a policy

veritas_run_pipeline triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

veritas_run_pipeline Rate-limited

veritas_run_pipeline 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": {
    "veritas_run_pipeline": {
      "limits": [
        {
          "counter": "veritas_run_pipeline_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 Mcp-Omega-Brain, so you can run agents against it safely.

FAQ

Questions about veritas_run_pipeline

What does the veritas_run_pipeline tool do? +

Runs the full 10-gate VERITAS pipeline: INTAKE → TYPE → DEPENDENCY → EVIDENCE → MATH → COST → INCENTIVE → SECURITY → ADVERSARY → TRACE/SEAL. It is categorised as a Execute tool in the Mcp-Omega-Brain MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on veritas_run_pipeline? +

Register the Mcp-Omega-Brain MCP server in PolicyLayer and add a rule for veritas_run_pipeline: 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 Mcp-Omega-Brain. Nothing to install.

What risk level is veritas_run_pipeline? +

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

Can I rate-limit veritas_run_pipeline? +

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

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

veritas_run_pipeline is provided by the Mcp-Omega-Brain MCP server (vrtxomega/omega-brain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.