New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

clear_step_runtime_override

Clear runtime overrides for a workflow step run, reverting to the workflow definition.

SERVERTodo for AI MCP Server SOURCEtodo-for-ai/todo-for-ai-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/todo-for-ai-todo-for-ai-mcp/clear-step-runtime-override.md

What clear_step_runtime_override does on Todo for AI MCP Server

AI agents call clear_step_runtime_override to permanently remove resources in Todo for AI MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why clear_step_runtime_override is rated Critical

An AI agent that decides to call clear_step_runtime_override doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Todo for AI MCP Server is gone. There is no undo for destructive operations.

Questions about clear_step_runtime_override

What does the clear_step_runtime_override tool do? +

Clear runtime overrides for a workflow step run, reverting to the workflow definition. It is categorised as a Destructive tool in the Todo for AI MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on clear_step_runtime_override? +

Register the Todo for AI MCP Server MCP server in PolicyLayer and add a rule for clear_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.

What risk level is clear_step_runtime_override? +

clear_step_runtime_override is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit clear_step_runtime_override? +

Yes. Add a rate_limit block to the clear_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.

How do I block clear_step_runtime_override completely? +

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

What MCP server provides clear_step_runtime_override? +

clear_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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Todo for AI MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.