// MCP TOOL REFERENCE

workflow_cancel

ServerBc Code Intelligence
CategoryDestructive

WHAT IT DOES

What workflow_cancel does on Bc Code Intelligence

AI agents call workflow_cancel to permanently remove resources in Bc Code Intelligence — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

THE RISK

Critical Risk

Why workflow_cancel needs a policy

Cancelling workflow sessions is irreversible — once cancelled, any in-progress work, state, and context of those sessions is lost and cannot be recovered. The 'cancel_all' option amplifies the blast radius significantly, potentially terminating all active AI-assisted development workflows simultaneously. This is a destructive action because session state cannot be restored after cancellation.

From the tool's definition Cancel a workflow session or clear all workflow sessions... cancel_all: true to cancel ALL active workflow sessions

Documented attack patterns abuse exactly the kind of access workflow_cancel gives an agent:

POLICY

How to control workflow_cancel

PolicyLayer is an MCP gateway — it sits between your AI agents and Bc Code Intelligence, and nothing reaches the server without passing your rules. This is the rule we recommend for workflow_cancel:

policy.json

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

workflow_cancel disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Bc Code Intelligence — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Bc Code Intelligence tools

Execute workflow_batch Apply batch operations to multiple pattern instances in a Workflow Engine v2 session. For Execute workflow_start Start a workflow session - a stateful checklist management system that drives agents throu Execute reload_layers Reload layers after configuration changes without restarting MCP server. Useful for testin Write create_layer_content Create a new topic, specialist, or prompt in a BC Code Intelligence layer with proper fron Write scaffold_layer_repo Create BC Code Intelligence layer folder structure with templates. Use this to bootstrap a Write set_workspace_info Set workspace root directory and available MCP server IDs. Enables project-specific knowle Write workflow_complete Complete a Workflow Engine v2 session and generate the final report. Call this when all f Read analyze_al_code Analyze AL code files in a workspace or specific files. IMPORTANT: Use workspace_path or f

All 27 Bc Code Intelligence tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Bc Code Intelligence → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about workflow_cancel

What does the workflow_cancel tool do? +

Cancel a workflow session or clear all workflow sessions. Use cases: - Cancel a stale/orphaned workflow from a previous session - Reset workflow state when restarting work - Clear all workflows to start fresh Options: - session_id: Cancel a specific workflow session - cancel_all: true to cancel ALL active workflow sessions. It is categorised as a Destructive tool in the Bc Code Intelligence 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 workflow_cancel? +

Register the Bc Code Intelligence MCP server in PolicyLayer and add a rule for workflow_cancel: 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 Bc Code Intelligence. Nothing to install.

What risk level is workflow_cancel? +

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

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

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

workflow_cancel is provided by the Bc Code Intelligence MCP server (jeremyvyska/bc-code-intelligence-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Bc Code Intelligence tool call.

Start from Bc Code Intelligence, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

27 Bc Code Intelligence tools catalogued and risk-classified — across an index of 43,000+ MCP servers.