Critical Risk →

remove_step

Remove a step from a workflow with optional next-pointer rewiring. When rewireNext is true (default): steps that pointed to the removed step are rewired to the removed step's next target. Entry condition criteria referencing the removed step are also cleaned up. Respects draft snapshot routing f...

Part of the Agentled MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@agentled/mcp-server Destructive Risk 4/5

AI agents may call remove_step to permanently remove or destroy resources in Agentled. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call remove_step in a loop, permanently destroying resources in Agentled. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

io-github-agentled-mcp-server.yaml
tools:
  remove_step:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Agentled policy for all 56 tools.

Tool Name remove_step
Category Destructive
MCP Server Agentled MCP Server
Risk Level Critical

View all 56 tools →

Agents calling destructive-class tools like remove_step have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

remove_step is one of the critical-risk operations in Agentled. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the remove_step tool do? +

Remove a step from a workflow with optional next-pointer rewiring. When rewireNext is true (default): steps that pointed to the removed step are rewired to the removed step's next target. Entry condition criteria referencing the removed step are also cleaned up. Respects draft snapshot routing for live workflows.. It is categorised as a Destructive tool in the Agentled 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 remove_step? +

Add a rule in your Intercept YAML policy under the tools section for remove_step. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Agentled MCP server.

What risk level is remove_step? +

remove_step 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 remove_step? +

Yes. Add a rate_limit block to the remove_step rule in your Intercept 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 remove_step completely? +

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

remove_step is provided by the Agentled MCP server (@agentled/mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Agentled

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.