This record as markdown: /tools/yanhuifair-godot-mcp/read-script.md
What read_script does on Godot
AI agents call read_script to retrieve information from Godot 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 | Path to script file (relative to project root) |
line_count | object | — | Number of lines to read (optional) |
line_start | object | — | Starting line (1-indexed, optional) |
Parameters from the server's own tool schema.
Why read_script is rated Low
This tool retrieves and queries script file contents. It performs a read-only operation that does not create, modify, delete, execute, or trigger any state changes. This is a straightforward data retrieval use case with minimal blast radius if misused—an agent could read sensitive source code but cannot cause operational damage.
From the tool's definition Tool name 'read_script' and description 'Read a script file with line numbers' explicitly indicate a retrieval operation with no side effects.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs read_script 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 read_script, this is the rule to start with:
read_script 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 Godot, apply this rule, and every read_script call is checked against it from then on.
Questions about read_script
Read a script file with line numbers. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
read_script accepts 3 parameters: path, line_count, line_start. 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 read_script: 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.
read_script 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 read_script 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 read_script. 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.
read_script 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