Low Risk

filesystem_list

List files and directories inside a Godot project

How to control filesystem_list ↓

AI agents call filesystem_list 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 queries the filesystem structure without modifying, deleting, or executing anything. It is a standard read operation that retrieves directory and file information for inspection purposes, consistent with the Read category definition of 'retrieves or queries data; no side effects (search, list, get, fetch)'.

From the tool's definition Tool name 'filesystem_list' and description 'List files and directories inside a Godot project' indicate a retrieval operation with no side effects.

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

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

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

List files and directories inside a Godot project. 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 filesystem_list? +

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

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

Can I rate-limit filesystem_list? +

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

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

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