set_project_root · GDScript Code Analyzer MCP: Risk & Policy

WHAT IT DOES

What set_project_root does on GDScript Code Analyzer

AI agents use set_project_root to create or update resources in GDScript Code Analyzer — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GDScript Code Analyzer environment.

WHY IT NEEDS A POLICY

Why set_project_root needs a policy

This tool creates or modifies the project root configuration and builds an index of GDScript files. While not destructive (the index can be reset), it is a state-mutating operation that affects subsequent tool behavior. It is reversible (can set a different root), so it qualifies as Write rather than Execute.

From the tool's definition Tool performs 'Set the project root directory' and 'will index all .gd files in the project' — this modifies analyzer state and creates/updates an index that persists across tool invocations.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_project_root Rate-limited

set_project_root stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_project_root": {
      "limits": [
        {
          "counter": "set_project_root_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches GDScript Code Analyzer, so you can run agents against it safely.

FAQ

Questions about set_project_root

What does the set_project_root tool do? +

Set the project root directory to enable project-wide analysis. This will index all .gd files in the project. It is categorised as a Write tool in the GDScript Code Analyzer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_project_root? +

Register the GDScript Code Analyzer MCP server in PolicyLayer and add a rule for set_project_root: 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 GDScript Code Analyzer. Nothing to install.

What risk level is set_project_root? +

set_project_root is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_project_root? +

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

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

set_project_root is provided by the GDScript Code Analyzer MCP server (minami110/mcp-gdscript). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.