get_all_project_settings
Get all project settings, optionally filtered by prefix
This record as markdown: /tools/keeveeg-godot-mcp/get-all-project-settings.md
What get_all_project_settings does on Godot
AI agents call get_all_project_settings 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 |
|---|---|---|---|
filter | string | — | Prefix filter (e.g. 'display/', 'input/') |
Parameters from the server's own tool schema.
Why get_all_project_settings is rated Low
This tool retrieves project configuration data without modifying, deleting, or executing code. It is a read-only query operation with no side effects. The blast radius is minimal as it only exposes configuration metadata that would typically be accessible to developers working on the project.
From the tool's definition Tool name is 'get_all_project_settings' with description 'Get all project settings, optionally filtered by prefix' — uses 'Get' verb and explicitly describes retrieval/querying functionality with optional filtering.
Attacks that exploit this kind of access
The rule that runs get_all_project_settings 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 get_all_project_settings, this is the rule to start with:
get_all_project_settings 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 get_all_project_settings call is checked against it from then on.
Questions about get_all_project_settings
Get all project settings, optionally filtered by prefix. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
get_all_project_settings accepts 1 parameter: filter. 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 get_all_project_settings: 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.
get_all_project_settings 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_all_project_settings 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_all_project_settings. 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_all_project_settings 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