project_setting_get
Get a project setting value from project.godot.
This record as markdown: /tools/chanceflow-godot-mcp/project-setting-get.md
What project_setting_get does on Godot
AI agents call project_setting_get 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 project_setting_get is rated Low
This tool queries and retrieves a configuration value from the Godot project settings file. It performs a read-only operation with no capability to modify, execute, or delete data. The blast radius of misuse is minimal—an attacker gains knowledge of project configuration but cannot alter the project or execute arbitrary code.
From the tool's definition Tool name uses 'get' which retrieves data; description states 'Get a project setting value' with no modification or side effects
Attacks that exploit this kind of access
The rule that runs project_setting_get 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 project_setting_get, this is the rule to start with:
project_setting_get 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 project_setting_get call is checked against it from then on.
Questions about project_setting_get
Get a project setting value from project.godot. 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 project_setting_get: 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.
project_setting_get 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_setting_get 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_setting_get. 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_setting_get 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