filesystem_scan

Trigger an editor rescan of the project filesystem so newly added or externally-changed files are picked up. Read-only side effect.

SERVERGodot Breakpoint SOURCEjlivingston-Cipher/godot-breakpoint-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/godot-breakpoint-mcp/filesystem-scan.md

WHAT IT DOES

What filesystem_scan does on Godot Breakpoint

AI agents invoke filesystem_scan to trigger actions in Godot Breakpoint. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why filesystem_scan is rated High

Although described as 'read-only side effect,' the tool triggers an active operation in the Godot editor (filesystem rescan), which constitutes executing an external action. It does not read/return data directly, nor does it write or destroy anything. The blast radius is low since it only rescans the filesystem without modifying any data.

From the tool's definition 'Trigger an editor rescan of the project filesystem' — this actively triggers an external operation in the Godot editor rather than simply reading data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs filesystem_scan 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 filesystem_scan, this is the rule to start with:

filesystem_scan Rate-limited

filesystem_scan stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "filesystem_scan": {
      "limits": [
        {
          "counter": "filesystem_scan_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Godot Breakpoint, apply this rule, and every filesystem_scan call is checked against it from then on.

FAQ

Questions about filesystem_scan

What does the filesystem_scan tool do? +

Trigger an editor rescan of the project filesystem so newly added or externally-changed files are picked up. Read-only side effect. It is categorised as a Execute tool in the Godot Breakpoint MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on filesystem_scan? +

Register the Godot Breakpoint MCP server in PolicyLayer and add a rule for filesystem_scan: 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.

What risk level is filesystem_scan? +

filesystem_scan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit filesystem_scan? +

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

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

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

KEEP EXPLORING

More on Godot Breakpoint, and thousands of servers like it.

This server

All 239 Godot Breakpoint tools → High-risk tools on this server →

Across the catalogue

run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →