Get the list of autoload singletons registered in the project.
AI agents call get_autoloads to retrieve information from Godot MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about registered autoload singletons in a Godot project. It performs a read-only query with no side effects, no code execution, and no data modification. The blast radius of misuse is minimal—an AI agent could only discover what autoloads exist in the project, which is informational only. This clearly fits the Read category (retrieves or queries data; no side effects).
From the tool's definition Tool name is 'get_autoloads' and description states 'Get the list of autoloads' — a query operation that retrieves configuration data without modifying or executing anything.
Attacks that exploit this kind of access
Get the list of autoload singletons registered in the project. It is categorised as a Read tool in the Godot MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Godot MCP Server MCP server in PolicyLayer and add a rule for get_autoloads: 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 MCP Server. Nothing to install.
get_autoloads 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 get_autoloads 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 get_autoloads. 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.
get_autoloads is provided by the Godot MCP Server MCP server (neondeex/godotmcp-pro-free-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →