High Risk →

workflow_execute

Start a Mistral Workflow execution. `workflowIdentifier` is the workflow name or ID (visible in mistral://workflows). `input` is a free-form JSON object matching the workflow's input schema. Modes: - waitForResult=false (default): returns immediately with execution_id and RUNNING status. ...

Single-target operation

Part of the Mistral MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

mistral-mcp Execute

AI agents invoke workflow_execute to trigger processes or run actions in Mistral. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

workflow_execute can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

io-github-swih-mistral-mcp.yaml
tools:
  workflow_execute:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Mistral policy for all 8 tools.

Tool Name workflow_execute
Category Execute
MCP Server Mistral MCP Server
Risk Level High

Agents calling execute-class tools like workflow_execute have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

workflow_execute is one of the high-risk operations in Mistral. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the workflow_execute tool do? +

Start a Mistral Workflow execution. `workflowIdentifier` is the workflow name or ID (visible in mistral://workflows). `input` is a free-form JSON object matching the workflow's input schema. Modes: - waitForResult=false (default): returns immediately with execution_id and RUNNING status. Poll workflow_status to track completion. - waitForResult=true: blocks until the workflow finishes and returns the result inline. Use timeoutSeconds (default 30) to cap the wait. Use deploymentName to target a specific deployment slot when multiple are configured.. It is categorised as a Execute tool in the Mistral MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on workflow_execute? +

Add a rule in your Intercept YAML policy under the tools section for workflow_execute. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mistral MCP server.

What risk level is workflow_execute? +

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

Can I rate-limit workflow_execute? +

Yes. Add a rate_limit block to the workflow_execute rule in your Intercept 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 workflow_execute completely? +

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

workflow_execute is provided by the Mistral MCP server (mistral-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

Currently onboarding teams running MCP in production.
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.

// REQUEST EARLY ACCESS

We're letting people in as fast as we can.

You're in the queue.

We'll be in touch as soon as we can let you in.