resource_save
Load a resource and (re-)save it, optionally to a new path and with ResourceSaver flags. DESTRUCTIVE (writes a file) — gated by confirmation. Shares subresources by reference; use resource_duplicate for an independent copy.
This record as markdown: /tools/breakpoint-mcp/resource-save.md
What resource_save does on Breakpoint
AI agents call resource_save to permanently remove resources in Breakpoint, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
flags | integer | — | ResourceSaver.SaverFlags bitmask (e.g. 32 = FLAG_COMPRESS) |
confirm | boolean | — | Auto-approve this destructive action (skip the confirmation prompt) |
to_path | string | — | Destination res:// path (default: overwrite from_path) |
from_path | string | Yes | Source resource res:// path |
Parameters from the server's own tool schema.
Why resource_save is rated Critical
The tool explicitly labels itself as DESTRUCTIVE and writes/overwrites files. Saving to a new path or re-saving an existing resource can overwrite existing data irreversibly. The mention of shared subresources by reference further increases blast radius, as overwriting could affect multiple dependent resources.
From the tool's definition DESTRUCTIVE (writes a file) — gated by confirmation. Shares subresources by reference
Attacks that exploit this kind of access
The rule that runs resource_save safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For resource_save, this is the rule to start with:
resource_save 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 Breakpoint, apply this rule, and every resource_save call is checked against it from then on.
Questions about resource_save
Load a resource and (re-)save it, optionally to a new path and with ResourceSaver flags. DESTRUCTIVE (writes a file) — gated by confirmation. Shares subresources by reference; use resource_duplicate for an independent copy. It is categorised as a Destructive tool in the Breakpoint MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
resource_save accepts 4 parameters: flags, confirm, to_path, from_path. Required: from_path. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for resource_save: 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 Breakpoint. Nothing to install.
resource_save 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 resource_save 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 resource_save. 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.
resource_save is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
Across the catalogue