set_step_runtime_override
Dynamically reconfigure a not-yet-terminal workflow step (runtime overrides). Only PENDING/WAITING steps accept start-time params; RUNNING steps accept only timeout_seconds/retry_count.
This record as markdown: /tools/todo-for-ai-todo-for-ai-mcp/set-step-runtime-override.md
What set_step_runtime_override does on Todo for AI MCP Server
AI agents use set_step_runtime_override to create or update resources in Todo for AI MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todo for AI MCP Server environment.
Why set_step_runtime_override is rated Medium
An AI agent can call set_step_runtime_override faster than any human can review: one bad instruction and it creates or modifies resources in Todo for AI MCP Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs set_step_runtime_override safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Todo for AI MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_step_runtime_override, this is the rule to start with:
set_step_runtime_override stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Todo for AI MCP Server, apply this rule, and every set_step_runtime_override call is checked against it from then on.
Questions about set_step_runtime_override
Dynamically reconfigure a not-yet-terminal workflow step (runtime overrides). Only PENDING/WAITING steps accept start-time params; RUNNING steps accept only timeout_seconds/retry_count. It is categorised as a Write tool in the Todo for AI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Todo for AI MCP Server MCP server in PolicyLayer and add a rule for set_step_runtime_override: 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 Todo for AI MCP Server. Nothing to install.
set_step_runtime_override is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_step_runtime_override 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 set_step_runtime_override. 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.
set_step_runtime_override is provided by the Todo for AI MCP Server MCP server (todo-for-ai/todo-for-ai-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Todo for AI MCP Server, and thousands of servers like it.
This server
Across the catalogue