Low Risk

get_script_index

Return GDScript files with class, base class, exported variables, and functions

How to control get_script_index ↓

AI agents call get_script_index 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

The tool retrieves and indexes script metadata for inspection purposes. It queries existing data without creating, modifying, or executing code. This is a safe read operation suitable for project analysis and documentation.

From the tool's definition Tool returns GDScript files with metadata (class, base class, exported variables, and functions). No modifications, deletions, or side effects—purely retrieval of project structure information.

Documented attack patterns abuse exactly the kind of access get_script_index 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 get_script_index:

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

get_script_index 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 get_script_index tool do? +

Return GDScript files with class, base class, exported variables, and functions. 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 get_script_index? +

Register the Godot Devtool MCP server in PolicyLayer and add a rule for get_script_index: 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 get_script_index? +

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

Can I rate-limit get_script_index? +

Yes. Add a rate_limit block to the get_script_index 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 get_script_index completely? +

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

get_script_index 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.