submit_workflow · Argo Workflow MCP Server MCP

WHAT IT DOES

What submit_workflow does on Argo Workflow MCP Server

AI agents invoke submit_workflow to trigger actions in Argo Workflow 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 submit_workflow needs a policy

Submitting a workflow runs arbitrary computational processes defined in the template. This is an Execute action as it triggers external operations whose effects depend on the workflow definition. The blast radius is high because workflow execution can trigger broad infrastructure actions, data processing, deployments, or other side effects depending on the template content.

From the tool's definition 'submit_workflow' and description '运行指定的 Workflow Template' (Run the specified Workflow Template) — triggers execution of a workflow template

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submit_workflow Rate-limited

submit_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": {
    "submit_workflow": {
      "limits": [
        {
          "counter": "submit_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 Argo Workflow MCP Server, so you can run agents against it safely.

FAQ

Questions about submit_workflow

What does the submit_workflow tool do? +

运行指定的 Workflow Template. It is categorised as a Execute tool in the Argo Workflow 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 submit_workflow? +

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

What risk level is submit_workflow? +

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

Can I rate-limit submit_workflow? +

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

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

submit_workflow is provided by the Argo Workflow MCP Server MCP server (yjx3097890/argo-workflow-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.