resource_get_import_settings
Read an asset's import metadata (.import): the importer and its parameters. Read-only. Returns imported=false when the asset has no .import sidecar.
This record as markdown: /tools/breakpoint-mcp/resource-get-import-settings.md
What resource_get_import_settings does on Breakpoint
AI agents call resource_get_import_settings to retrieve information from Breakpoint without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Asset res:// path (e.g. res://icon.png) |
Parameters from the server's own tool schema.
Why resource_get_import_settings is rated Low
This tool retrieves metadata about assets without modifying, executing, or deleting anything. It is a straightforward read operation that queries import settings information.
From the tool's definition Tool description explicitly states 'Read-only' and describes retrieving 'an asset's import metadata' and 'importer and its parameters', which are data retrieval operations with no side effects.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs resource_get_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_get_import_settings, this is the rule to start with:
resource_get_import_settings is read-only, so it stays allowed. 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_get_import_settings call is checked against it from then on.
Questions about resource_get_import_settings
Read an asset's import metadata (.import): the importer and its parameters. Read-only. Returns imported=false when the asset has no .import sidecar. It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.
resource_get_import_settings accepts 1 parameter: path. Required: 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_get_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_get_import_settings is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the resource_get_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_get_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_get_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.
This server
Across the catalogue