Low Risk

find_empty_directories

find_empty_directories

How to control find_empty_directories ↓

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

Low Risk

This tool retrieves/queries filesystem state to locate empty directories. It has no side effects—no data is created, modified, deleted, or executed. The operation is a read-only traversal. Confidence is slightly reduced due to the missing description, but the tool name and server context strongly indicate a non-destructive information retrieval function.

From the tool's definition Tool name 'find_empty_directories' indicates a filesystem query operation that identifies directories matching a condition (being empty).

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

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

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

find_empty_directories 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 MCP Filesystem Server — 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 find_empty_directories tool do? +

find_empty_directories. It is categorised as a Read tool in the MCP Filesystem Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on find_empty_directories? +

Register the MCP Filesystem Server MCP server in PolicyLayer and add a rule for find_empty_directories: 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 MCP Filesystem Server. Nothing to install.

What risk level is find_empty_directories? +

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

Can I rate-limit find_empty_directories? +

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

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

find_empty_directories is provided by the MCP Filesystem Server MCP server (safurrier/mcp-filesystem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Filesystem Server tool call.

Deterministic rules across all 21 MCP Filesystem Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

21 MCP Filesystem Server 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.