AI agents invoke change_taskrun_state 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.
Changing the state of a task run in a workflow orchestration system like Kestra is an execution-level operation — it affects the runtime behavior of workflows. This could resume, pause, fail, or otherwise alter in-flight executions. The sibling tools (execute_flow, force_run_execution, backfill_executions) confirm this server manages workflow execution states.
From the tool's definition Tool name 'change_taskrun_state' suggests modifying the execution state of a task run, which is an operational action affecting workflow execution. Description is empty, lowering confidence.
Documented attack patterns abuse exactly the kind of access change_taskrun_state 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 change_taskrun_state:
{
"version": "1",
"default": "deny",
"tools": {
"change_taskrun_state": {
"limits": [
{
"counter": "change_taskrun_state_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}change_taskrun_state 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.
change_taskrun_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 change_taskrun_state: 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.
change_taskrun_state 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 change_taskrun_state 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 change_taskrun_state. 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.
change_taskrun_state 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.