make_directory · MCP4Modal Sandbox MCP: Risk & Policy

WHAT IT DOES

What make_directory does on MCP4Modal Sandbox

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

WHY IT NEEDS A POLICY

Why make_directory needs a policy

make_directory creates new directories within a sandbox environment. This is a Write operation—it modifies the file system reversibly (directories can be deleted). While the empty description lowers confidence slightly, the name is explicit and the server context clearly establishes this as filesystem manipulation.

From the tool's definition Tool name 'make_directory' indicates directory creation. Tool description is empty but context shows this is part of a sandbox management system with sibling tools like 'remove_path', 'write_file_content_to_sandbox', and 'execute_command'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

make_directory Rate-limited

make_directory 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": {
    "make_directory": {
      "limits": [
        {
          "counter": "make_directory_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 MCP4Modal Sandbox, so you can run agents against it safely.

FAQ

Questions about make_directory

What does the make_directory tool do? +

make_directory. It is categorised as a Write tool in the MCP4Modal Sandbox MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on make_directory? +

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

What risk level is make_directory? +

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

Can I rate-limit make_directory? +

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

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

make_directory is provided by the MCP4Modal Sandbox MCP server (milkymap/mcp4modal_sandbox). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.