resource_duplicate
Load a resource, duplicate it (optionally deep, cloning subresources), and save the copy to a new path. DESTRUCTIVE (writes a file) — gated by confirmation.
This record as markdown: /tools/breakpoint-mcp/resource-duplicate.md
What resource_duplicate does on Breakpoint
AI agents use resource_duplicate to create or update resources in Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Breakpoint environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
deep | boolean | — | Deep-duplicate subresources (default false) |
path | string | Yes | Source resource res:// path |
confirm | boolean | — | Auto-approve this destructive action (skip the confirmation prompt) |
to_path | string | Yes | Destination res:// path for the copy |
Parameters from the server's own tool schema.
Why resource_duplicate is rated Medium
This tool creates a new file (a duplicate resource at a new path), which is a reversible modification operation characteristic of Write category. While the description uses the word 'DESTRUCTIVE', the actual operation—duplicating and saving to a new path—does not delete or overwrite existing data. The confirmation gate mitigates accidental misuse.
From the tool's definition Tool description states it 'duplicate[s] it... and save[s] the copy to a new path' and mentions 'writes a file'. The description itself labels it 'DESTRUCTIVE' but this refers to the file write operation, not data deletion.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs resource_duplicate 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_duplicate, this is the rule to start with:
resource_duplicate stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every resource_duplicate call is checked against it from then on.
Questions about resource_duplicate
Load a resource, duplicate it (optionally deep, cloning subresources), and save the copy to a new path. DESTRUCTIVE (writes a file) — gated by confirmation. It is categorised as a Write tool in the Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
resource_duplicate accepts 4 parameters: deep, path, confirm, to_path. Required: path, to_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_duplicate: 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_duplicate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the resource_duplicate 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_duplicate. 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_duplicate 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.
This server
Across the catalogue