read_resource
Read a Godot resource file (.tres, .res) and get its properties
This record as markdown: /tools/keeveeg-godot-mcp/read-resource.md
What read_resource does on Godot
AI agents call read_resource 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 | Resource file path (e.g. 'res://assets/theme.tres') |
Parameters from the server's own tool schema.
Why read_resource is rated Low
This tool retrieves and queries properties from Godot resource files without modifying, deleting, or executing operations. It has no side effects beyond returning information, making it a Read category risk with low severity.
From the tool's definition Tool name is 'read_resource' and description explicitly states 'Read a Godot resource file (.tres, .res) and get its properties' — the verb 'Read' and 'get' indicate data retrieval with no modification.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs read_resource 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_resource, this is the rule to start with:
read_resource 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_resource call is checked against it from then on.
Questions about read_resource
Read a Godot resource file (.tres, .res) and get its properties. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
read_resource accepts 1 parameter: path. 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_resource: 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_resource 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_resource 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_resource. 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_resource 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.
More on Godot, and thousands of servers like it.
This server
Across the catalogue