agentbrush_remove_background
Strip the background from a PNG/JPG/WebP and return a transparent PNG. Runs locally — no token charge. Typical use: generate an image with background: 'opaque', then call agentbrush_remove_background on the saved file. image_path must be an absolute path to an existing PNG/JPG/WebP file. output_d...
This record as markdown: /tools/dev-agentbrush-mcp-server/agentbrush-remove-background.md
What agentbrush_remove_background does on Mcp Server
AI agents call agentbrush_remove_background to permanently remove resources in Mcp Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
image_path | string | Yes | Absolute path to a PNG/JPG/WebP image file. |
output_dir | string | — | Directory to save the resulting PNG. Defaults to the same directory as the source image. |
Parameters from the server's own tool schema.
Why agentbrush_remove_background is rated Critical
An AI agent that decides to call agentbrush_remove_background doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Mcp Server is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs agentbrush_remove_background safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For agentbrush_remove_background, this is the rule to start with:
agentbrush_remove_background 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 Mcp Server, apply this rule, and every agentbrush_remove_background call is checked against it from then on.
Questions about agentbrush_remove_background
Strip the background from a PNG/JPG/WebP and return a transparent PNG. Runs locally — no token charge. Typical use: generate an image with background: 'opaque', then call agentbrush_remove_background on the saved file. image_path must be an absolute path to an existing PNG/JPG/WebP file. output_dir is optional — defaults to the same directory as the source image. Returns the absolute path of the new PNG with a transparent background. It is categorised as a Destructive tool in the Mcp Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
agentbrush_remove_background accepts 2 parameters: image_path, output_dir. Required: image_path. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Server MCP server in PolicyLayer and add a rule for agentbrush_remove_background: 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 Mcp Server. Nothing to install.
agentbrush_remove_background 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 agentbrush_remove_background 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 agentbrush_remove_background. 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.
agentbrush_remove_background is provided by the Mcp Server MCP server (@agentbrush/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Server, and thousands of servers like it.
Across the catalogue