editor_open_script_at_line
Open a script in the editor and jump to a given line/column.
This record as markdown: /tools/yanhuifair-godot-mcp/editor-open-script-at-line.md
What editor_open_script_at_line does on Godot
AI agents use editor_open_script_at_line 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 |
|---|---|---|---|
line | object | — | Line to jump to (1-based) |
path | string | Yes | Script path, e.g. res://player.gd |
column | object | — | Column to place the caret at |
grab_focus | object | — | Focus the script editor after opening |
Parameters from the server's own tool schema.
Why editor_open_script_at_line is rated Medium
An AI agent can call editor_open_script_at_line faster than any human can review: one bad instruction and it creates or modifies resources in Godot by the hundred, each call as confident as the last.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs editor_open_script_at_line 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 editor_open_script_at_line, this is the rule to start with:
editor_open_script_at_line 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 editor_open_script_at_line call is checked against it from then on.
Questions about editor_open_script_at_line
Open a script in the editor and jump to a given line/column. 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.
editor_open_script_at_line accepts 4 parameters: line, path, column, grab_focus. 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 editor_open_script_at_line: 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.
editor_open_script_at_line 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 editor_open_script_at_line 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 editor_open_script_at_line. 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.
editor_open_script_at_line is provided by the Godot MCP server (@yanhuifair/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