remove_background
Remove the background from an existing image, leaving the main subject isolated on a transparent background (PNG). Routing: "isolate the subject", "make background transparent", "remove background" → use this (1 credit) [sensitive-tier — first use may require a manager's approval; a from-now-on a...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/remove-background.md
What remove_background does on Freedom Mcp
AI agents call remove_background to permanently remove resources in Freedom Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
folder | string | — | Optional Media gallery folder to file this into (freeform name, e.g. "q3-campaign" or "brand-assets"). Shown as a folder chip on the /media page. Reuse an exist |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
image_url | string | — | URL of the raster image to process. |
artifact_id | string | — | ID of an existing artifact from the MEDIA block. |
folder_name | string | — | Subfolder name for Drive save. |
save_to_drive | boolean | — | If true, saves to Drive. |
Parameters from the server's own tool schema.
Why remove_background is rated Critical
An AI agent that decides to call remove_background doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Freedom Mcp is gone. There is no undo for destructive operations.
Risk signalsAccepts file system path (folder)
Attacks that exploit this kind of access
The rule that runs remove_background safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freedom Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_background, this is the rule to start with:
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 Freedom Mcp, apply this rule, and every remove_background call is checked against it from then on.
Questions about remove_background
Remove the background from an existing image, leaving the main subject isolated on a transparent background (PNG). Routing: "isolate the subject", "make background transparent", "remove background" → use this (1 credit) [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.]. It is categorised as a Destructive tool in the Freedom Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
remove_background accepts 6 parameters: folder, companyId, image_url, artifact_id, folder_name, save_to_drive. Required: companyId. The full parameter table on this page comes from the server's own tool schema.
Register the Freedom MCP server in PolicyLayer and add a rule for 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 Freedom Mcp. Nothing to install.
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 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 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.
remove_background is provided by the Freedom MCP server (https://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freedom, and thousands of servers like it.
Across the catalogue