Create multiple specified directories (including intermediate ones).
AI agents use create_directories to create or update resources in Filesystem — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Filesystem environment.
Creating directories is a write operation that modifies the file system structure. While not destructive (directories can be deleted), it irreversibly changes the file system state. Severity is medium rather than high because directory creation is a common, low-blast-radius operation compared to deleting or overwriting critical files, though it could enable further harmful operations.
From the tool's definition Tool creates directories (irreversible file system operations that persist on disk). Tool name 'create_directories' explicitly states creation action. Description states 'Create multiple specified directories (including intermediate ones).'
Documented attack patterns abuse exactly the kind of access create_directories gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Filesystem, and nothing reaches the server without passing your rules. This is the rule we recommend for create_directories:
{
"version": "1",
"default": "deny",
"tools": {
"create_directories": {
"limits": [
{
"counter": "create_directories_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_directories 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 multiple specified directories (including intermediate ones). It is categorised as a Write tool in the Filesystem MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Filesystem MCP server in PolicyLayer and add a rule for create_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 Filesystem. Nothing to install.
create_directories 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_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.
Set action: deny in the PolicyLayer policy for create_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.
create_directories is provided by the Filesystem MCP server (sylphxai/filesystem-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Filesystem, 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.
13 Filesystem tools catalogued and risk-classified — across an index of 43,000+ MCP servers.