resource_set_import_settings
Update import parameters in an asset's .import metadata and trigger a reimport. DESTRUCTIVE (rewrites metadata + reimports) — gated by confirmation. Errors if the asset has no .import sidecar.
This record as markdown: /tools/breakpoint-mcp/resource-set-import-settings.md
What resource_set_import_settings does on Breakpoint
AI agents call resource_set_import_settings 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 |
|---|---|---|---|
path | string | Yes | Asset res:// path |
confirm | boolean | — | Auto-approve this destructive action (skip the confirmation prompt) |
reimport | boolean | — | Reimport after writing (default true) |
settings | object | Yes | Import params to set (name -> JSON scalar or __type__-tagged Variant) |
Parameters from the server's own tool schema.
Why resource_set_import_settings is rated Critical
The tool explicitly labels itself as DESTRUCTIVE, as it rewrites .import metadata files and triggers a reimport of assets. Overwriting metadata is not easily reversible, and triggering a reimport can alter how assets are processed in the project. This falls squarely in the Destructive category with high severity since misuse could corrupt asset configurations across a project.
From the tool's definition DESTRUCTIVE (rewrites metadata + reimports) — gated by confirmation. Errors if the asset has no .import sidecar.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs resource_set_import_settings 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_set_import_settings, this is the rule to start with:
resource_set_import_settings 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_set_import_settings call is checked against it from then on.
Questions about resource_set_import_settings
Update import parameters in an asset's .import metadata and trigger a reimport. DESTRUCTIVE (rewrites metadata + reimports) — gated by confirmation. Errors if the asset has no .import sidecar. 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_set_import_settings accepts 4 parameters: path, confirm, reimport, settings. Required: path, settings. 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_set_import_settings: 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_set_import_settings 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_set_import_settings 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_set_import_settings. 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_set_import_settings 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