Low Risk

get_directory_info

Get directory contents and info

How to control get_directory_info ↓

What get_directory_info does on Mcp Wsl Exec

AI agents call get_directory_info to retrieve information from Mcp Wsl Exec without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_directory_info needs a policy

This tool performs a read-only query of directory structure and metadata. It retrieves information without creating, modifying, executing, or deleting data. The presence of validation and injection protection on the server indicates security controls that would further constrain any potential misuse. The blast radius of incorrect directory information disclosure is minimal compared to other tool categories.

From the tool's definition Tool name 'get_directory_info' and description 'Get directory contents and info' indicate retrieval of file system metadata with no modification or execution capability.

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

How to control get_directory_info

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

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

get_directory_info 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 Wsl Exec — 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.

Related tools and policies

Go deeper

Questions about get_directory_info

What does the get_directory_info tool do? +

Get directory contents and info. It is categorised as a Read tool in the Mcp Wsl Exec MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_directory_info? +

Register the Mcp Wsl Exec MCP server in PolicyLayer and add a rule for get_directory_info: 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 Wsl Exec. Nothing to install.

What risk level is get_directory_info? +

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

Can I rate-limit get_directory_info? +

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

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

get_directory_info is provided by the Mcp Wsl Exec MCP server (spences10/mcp-wsl-exec). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Wsl Exec tool call.

Start from Mcp Wsl Exec, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

7 Mcp Wsl Exec tools catalogued and risk-classified — across an index of 43,000+ 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.