AI agents use create_directory to create or update resources in Filesystem MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Filesystem MCP Server environment.
Creating a directory is a Write operation—it modifies the filesystem state reversibly (the directory can be deleted). It's not Destructive because the action is not irreversible. Severity is medium because uncontrolled directory creation could fill disk space or pollute the filesystem structure, but the impact is typically containable and reversible.
From the tool's definition Tool name is 'create_directory' which creates a new directory on the filesystem. The description is empty, but the name and sibling tools (delete_file, modify_file, move_file, read_file) indicate this server manages filesystem operations where…
Documented attack patterns abuse exactly the kind of access create_directory gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Filesystem MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_directory:
{
"version": "1",
"default": "deny",
"tools": {
"create_directory": {
"limits": [
{
"counter": "create_directory_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_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.
Free to start. No card required.
create_directory. It is categorised as a Write tool in the Filesystem MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Filesystem MCP Server MCP server in PolicyLayer and add a rule for create_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 Filesystem MCP Server. Nothing to install.
create_directory is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_directory is provided by the Filesystem MCP Server MCP server (mark3labs/mcp-filesystem-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Filesystem MCP Server, 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.
14 Filesystem MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.