remove_bg
POST /v5/tools/remove_bg. 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/remove-bg.md
What remove_bg does on Bannerbear Mcp Cli
AI agents call remove_bg 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 |
|---|---|---|---|
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. |
payload | object | — | Complete current native JSON body. Use payload or payload_file exclusively. |
payload_file | string | — | Regular non-symlink local JSON file, at most 1 MiB. |
Parameters from the server's own tool schema.
Why remove_bg is rated Critical
An AI agent that decides to call remove_bg 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.
Risk signalsAccepts raw HTML/template content (payload)
Attacks that exploit this kind of access
The rule that runs remove_bg 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 remove_bg, this is the rule to start with:
remove_bg 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 remove_bg call is checked against it from then on.
Questions about remove_bg
POST /v5/tools/remove_bg. 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.
remove_bg accepts 4 parameters: account, confirm, payload, payload_file. 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 remove_bg: 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.
remove_bg 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 remove_bg 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 remove_bg. 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.
remove_bg 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