remove_workflow

Remove a dynamic workflow by name.

SERVERFrontmcp SOURCEagentfront/frontmcp

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/frontmcp/remove-workflow.md

WHAT IT DOES

What remove_workflow does on Frontmcp

AI agents call remove_workflow to permanently remove resources in Frontmcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why remove_workflow is rated Critical

Removing a workflow is an irreversible operation that eliminates a stored workflow configuration. This cannot be trivially undone and would prevent execution of that workflow going forward.

From the tool's definition Tool name contains 'remove' and description states 'Remove a dynamic workflow by name.' The verb 'remove' in the context of workflow management typically indicates deletion or permanent removal of a configuration or process.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs remove_workflow safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Frontmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_workflow, this is the rule to start with:

remove_workflow Hidden

remove_workflow is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_workflow"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Frontmcp, apply this rule, and every remove_workflow call is checked against it from then on.

FAQ

Questions about remove_workflow

What does the remove_workflow tool do? +

Remove a dynamic workflow by name. It is categorised as a Destructive tool in the Frontmcp 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_workflow? +

Register the Front MCP server in PolicyLayer and add a rule for remove_workflow: 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 Frontmcp. Nothing to install.

What risk level is remove_workflow? +

remove_workflow 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_workflow? +

Yes. Add a rate_limit block to the remove_workflow 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 remove_workflow completely? +

Set action: deny in the PolicyLayer policy for remove_workflow. 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_workflow? +

remove_workflow is provided by the Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Front, and thousands of servers like it.

This server

All 206 Front tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →