This record as markdown: /tools/chanceflow-godot-mcp/resource-list.md
What resource_list does on Godot
AI agents call resource_list 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.
Why resource_list is rated Low
The 'list' suffix strongly suggests data retrieval with no side effects. Within a game engine context, listing resources (animations, autoloads, etc.) is a non-destructive read operation. Although the description is empty, the naming convention and parallels with other list tools on the server provide high confidence this is a Read operation. No evidence of modification, deletion, execution, or financial impact.
From the tool's definition Tool name 'resource_list' with context from sibling tools (animation_list, autoload_list) indicates a listing/querying function. The server's purpose is interaction with Godot, and this tool fits the pattern of read-only resource enumeration.
Attacks that exploit this kind of access
The rule that runs resource_list 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 resource_list, this is the rule to start with:
resource_list 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 resource_list call is checked against it from then on.
Questions about resource_list
resource_list is a read tool on the Godot MCP server. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
Register the Godot MCP server in PolicyLayer and add a rule for resource_list: 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.
resource_list 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 resource_list 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 resource_list. 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.
resource_list is provided by the Godot MCP server (chanceflow/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