delete_workflow
DELETE /v5/workflows/{uid}. Current Bannerbear V5 operation; provider scopes, locks and credits apply. Mandatory confirmation before provider execution; one submission only.
This record as markdown: /tools/thenavidm-bannerbear-mcp-cli/delete-workflow.md
What delete_workflow does on Bannerbear Mcp Cli
AI agents call delete_workflow to permanently remove resources in Bannerbear Mcp Cli, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
uid | string | Yes | |
account | string | — | Exact private workspace profile label; no fallback to another profile key. |
confirm | boolean | — | Set true only when the user asked for exactly this action. |
Parameters from the server's own tool schema.
Why delete_workflow is rated Critical
An AI agent that decides to call delete_workflow doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Bannerbear Mcp Cli is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs delete_workflow safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bannerbear Mcp Cli, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_workflow, this is the rule to start with:
delete_workflow is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Bannerbear Mcp Cli, apply this rule, and every delete_workflow call is checked against it from then on.
Questions about delete_workflow
DELETE /v5/workflows/{uid}. Current Bannerbear V5 operation; provider scopes, locks and credits apply. Mandatory confirmation before provider execution; one submission only. It is categorised as a Destructive tool in the Bannerbear Mcp Cli MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_workflow accepts 3 parameters: uid, account, confirm. Required: uid. The full parameter table on this page comes from the server's own tool schema.
Register the Bannerbear Mcp Cli MCP server in PolicyLayer and add a rule for delete_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 Bannerbear Mcp Cli. Nothing to install.
delete_workflow is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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.
Set action: deny in the PolicyLayer policy for delete_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.
delete_workflow is provided by the Bannerbear Mcp Cli MCP server (@thenavidm/bannerbear-mcp-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Bannerbear Mcp Cli, and thousands of servers like it.
Across the catalogue