project_list_settings
List ProjectSettings keys and values, optionally filtered by a dotted-key prefix (e.g. \
This record as markdown: /tools/godot-breakpoint-mcp/project-list-settings.md
What project_list_settings does on Godot Breakpoint
AI agents call project_list_settings to retrieve information from Godot Breakpoint without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why project_list_settings is rated Low
This tool queries and retrieves project settings configuration data. It performs no modification, deletion, code execution, or financial operations. The filtering capability by dotted-key prefix is a standard read operation. Blast radius is minimal—it only exposes existing configuration metadata that a developer would already have access to within the Godot editor.
From the tool's definition Tool name contains 'list' and description states 'List ProjectSettings keys and values'; explicitly a read operation that retrieves configuration data without modification.
Attacks that exploit this kind of access
The rule that runs project_list_settings safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For project_list_settings, this is the rule to start with:
project_list_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 Breakpoint, apply this rule, and every project_list_settings call is checked against it from then on.
Questions about project_list_settings
List ProjectSettings keys and values, optionally filtered by a dotted-key prefix (e.g. \. It is categorised as a Read tool in the Godot Breakpoint MCP Server, which means it retrieves data without modifying state.
Register the Godot Breakpoint MCP server in PolicyLayer and add a rule for project_list_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 Breakpoint. Nothing to install.
project_list_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 project_list_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 project_list_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.
project_list_settings is provided by the Godot Breakpoint MCP server (jlivingston-Cipher/godot-breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot Breakpoint, and thousands of servers like it.
This server
Across the catalogue