Force run an execution only if it is in CREATED, PAUSED, or QUEUED state.
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.
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
Documented attack patterns abuse exactly the kind of access force_run_execution gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kestra Python MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for force_run_execution:
{
"version": "1",
"default": "deny",
"tools": {
"force_run_execution": {
"limits": [
{
"counter": "force_run_execution_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
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.
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.
force_run_execution is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
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.
Start from Kestra Python MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
39 Kestra Python MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.