import_resource
Import a file as a resource with optional import settings
This record as markdown: /tools/keeveeg-godot-mcp/import-resource.md
What import_resource does on Godot
AI agents use import_resource to create or update resources in Godot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | File path to import (e.g. 'res://assets/model.fbx') |
settings | object | — | Optional property key-value pairs |
Parameters from the server's own tool schema.
Why import_resource is rated Medium
Importing a file as a resource modifies the project state by adding or replacing resources. While not destructive (can be undone), it is a Write operation that creates new project artifacts. Severity is high because a malicious agent could import malicious resources, corrupt asset pipelines, or inject unwanted dependencies into the game project.
From the tool's definition Tool name 'import_resource' combined with description 'Import a file as a resource with optional import settings' indicates creation/modification of project resources.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs import_resource safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For import_resource, this is the rule to start with:
import_resource 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 Godot, apply this rule, and every import_resource call is checked against it from then on.
Questions about import_resource
Import a file as a resource with optional import settings. It is categorised as a Write tool in the Godot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
import_resource accepts 2 parameters: path, settings. Required: path. The full parameter table on this page comes from the server's own tool schema.
Register the Godot MCP server in PolicyLayer and add a rule for import_resource: 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 Godot. Nothing to install.
import_resource 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 import_resource 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 import_resource. 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.
import_resource is provided by the Godot MCP server (@keeveeg/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot, and thousands of servers like it.
This server
Across the catalogue