AI agents call read_script_file to retrieve information from Godot Devtool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries file data (GDScript source code) without creating, modifying, deleting, or executing anything. It is a pure read operation analogous to 'cat' or 'get'. While misuse could expose sensitive logic or credentials embedded in scripts, the tool itself performs no destructive or executable action.
From the tool's definition Tool name 'read_script_file' and description 'Read a GDScript file from a Godot project' explicitly indicate retrieval of file contents with no modification or side effects.
Documented attack patterns abuse exactly the kind of access read_script_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Godot Devtool, and nothing reaches the server without passing your rules. This is the rule we recommend for read_script_file:
{
"version": "1",
"default": "deny",
"tools": {
"read_script_file": {}
}
}read_script_file is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Read a GDScript file from a Godot project. It is categorised as a Read tool in the Godot Devtool MCP Server, which means it retrieves data without modifying state.
Register the Godot Devtool MCP server in PolicyLayer and add a rule for read_script_file: 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 Devtool. Nothing to install.
read_script_file 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_file 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_file. 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_file is provided by the Godot Devtool MCP server (wangdiandao/godot-devtool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 101 Godot Devtool tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
101 Godot Devtool tools catalogued and risk-classified — across an index of 42,500+ MCP servers.