godot_import
Headless (re)import of project assets. Runs to completion and returns exit code + logs. Exposed as an MCP task (poll/await/cancel via tasks/get, tasks/result, tasks/cancel).
This record as markdown: /tools/breakpoint-mcp/godot-import.md
What godot_import does on Breakpoint
AI agents invoke godot_import to trigger actions in Breakpoint. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
timeout_ms | integer | — | Max run time (default 600000) |
Parameters from the server's own tool schema.
Why godot_import is rated High
This tool executes an external process (headless Godot import pipeline) that runs to completion and returns an exit code. It triggers an external operation whose effects depend on arguments (reimporting assets modifies project files), making it Execute-category. Severity is medium as misuse could corrupt project assets but is generally recoverable.
From the tool's definition "Headless (re)import of project assets. Runs to completion and returns exit code + logs"
Attacks that exploit this kind of access
The rule that runs godot_import 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 godot_import, this is the rule to start with:
godot_import stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 godot_import call is checked against it from then on.
Questions about godot_import
Headless (re)import of project assets. Runs to completion and returns exit code + logs. Exposed as an MCP task (poll/await/cancel via tasks/get, tasks/result, tasks/cancel). It is categorised as a Execute tool in the Breakpoint MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
godot_import accepts 1 parameter: timeout_ms. 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 godot_import: 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.
godot_import is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the godot_import 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 godot_import. 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.
godot_import 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