force_run_execution

Force run an execution only if it is in CREATED, PAUSED, or QUEUED state.

SERVERKestra Python MCP Server SOURCEkestra-io/mcp-server-python

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kestra-io-mcp-server-python/force-run-execution.md

WHAT IT DOES

What force_run_execution does on Kestra Python MCP Server

AI agents invoke force_run_execution to trigger actions in Kestra Python 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.

RISK

Why force_run_execution is rated High

This tool forcibly triggers/resumes a workflow execution, which is an Execute-category action. It causes external operations to run depending on which execution is targeted. Misuse could trigger unintended workflows or resume paused workflows prematurely, causing high-impact side effects in production systems.

From the tool's definition 'Force run an execution' - triggers execution of a workflow; operates on executions in CREATED, PAUSED, or QUEUED state

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs force_run_execution safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Kestra Python MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For force_run_execution, this is the rule to start with:

force_run_execution Rate-limited

force_run_execution 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": {
    "force_run_execution": {
      "limits": [
        {
          "counter": "force_run_execution_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Kestra Python MCP Server, apply this rule, and every force_run_execution call is checked against it from then on.

FAQ

Questions about force_run_execution

What does the force_run_execution tool do? +

Force run an execution only if it is in CREATED, PAUSED, or QUEUED state. It is categorised as a Execute tool in the Kestra Python 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 force_run_execution? +

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

What risk level is force_run_execution? +

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

Can I rate-limit force_run_execution? +

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

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

force_run_execution is provided by the Kestra Python MCP Server MCP server (kestra-io/mcp-server-python). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Kestra Python MCP Server, and thousands of servers like it.

This server

All 39 Kestra Python MCP Server tools → High-risk tools on this server →

Across the catalogue

run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →