read_script

Read the contents of a GDScript file

SERVERGodot SOURCE@keeveeg/godot-mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/keeveeg-godot-mcp/read-script.md

WHAT IT DOES

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	Script file path (e.g. 'res://scripts/player.gd')

Parameters from the server's own tool schema.

RISK

Why read_script is rated Low

This tool performs a simple read operation to retrieve GDScript file content. It does not create, modify, delete, or execute any code. The action is purely informational with no capability to affect the Godot project state beyond data retrieval.

From the tool's definition Tool name 'read_script' and description 'Read the contents of a GDScript file' explicitly indicate retrieval of file contents with no modification or side effects.

Risk signalsAccepts file system path (path)

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Allowed

read_script is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "read_script": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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.

FAQ

Questions about read_script

What does the read_script tool do? +

Read the contents of a GDScript file. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.

What parameters does read_script accept? +

read_script accepts 1 parameter: path. Required: path. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on read_script? +

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.

What risk level is read_script? +

read_script is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit read_script? +

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.

How do I block read_script completely? +

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.

What MCP server provides read_script? +

read_script 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.

KEEP EXPLORING

More on Godot, and thousands of servers like it.

This server

All 321 Godot tools →

Across the catalogue

claude_read_file on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →