Low Risk

project_get_settings

Read Godot project.godot settings by section or section/key list

How to control project_get_settings ↓

AI agents call project_get_settings to retrieve information from Godot Devtool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool only reads and retrieves Godot project settings from the project.godot file. It performs a query operation with no side effects, no code execution, and no data modification. The verb 'Read' and absence of any write/delete/execute capability places it firmly in the Read category.

From the tool's definition Tool name 'project_get_settings' and description 'Read Godot project.godot settings by section or section/key list' explicitly indicate retrieval of configuration data with no modification capability.

Documented attack patterns abuse exactly the kind of access project_get_settings gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Godot Devtool, and nothing reaches the server without passing your rules. This is the rule we recommend for project_get_settings:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "project_get_settings": {}
  }
}

project_get_settings is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Godot Devtool — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the project_get_settings tool do? +

Read Godot project.godot settings by section or section/key list. It is categorised as a Read tool in the Godot Devtool MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on project_get_settings? +

Register the Godot Devtool MCP server in PolicyLayer and add a rule for project_get_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 Devtool. Nothing to install.

What risk level is project_get_settings? +

project_get_settings is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit project_get_settings? +

Yes. Add a rate_limit block to the project_get_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.

How do I block project_get_settings completely? +

Set action: deny in the PolicyLayer policy for project_get_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.

What MCP server provides project_get_settings? +

project_get_settings is provided by the Godot Devtool MCP server (wangdiandao/godot-devtool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Godot Devtool tool call.

Deterministic rules across all 101 Godot Devtool tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

101 Godot Devtool tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.