create_directory
Create a new directory or ensure a directory exists. Can create multiple nested directories in one operation. If the directory already exists, this operation will succeed silently. Perfect for setting up directory structures for projects or ensuring required paths exist. Only works within allowed...
This record as markdown: /tools/filesystem/create-directory.md
What create_directory does on Filesystem
AI agents use create_directory 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes |
Parameters from the server's own tool schema.
Why create_directory is rated Medium
Creating directories is a write operation that modifies the filesystem by adding new structures. It is reversible (directories can be deleted) and has limited blast radius since it only creates empty directory structures within allowed paths. Severity is low because accidental directory creation causes minimal harm and does not affect existing data or execute code.
From the tool's definition Tool description states it 'Create[s] a new directory' and 'can create multiple nested directories in one operation.' This is a reversible creation operation. The tool is constrained to 'allowed directories' only.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs create_directory safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Filesystem, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_directory, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Filesystem, apply this rule, and every create_directory call is checked against it from then on.
Questions about create_directory
Create a new directory or ensure a directory exists. Can create multiple nested directories in one operation. If the directory already exists, this operation will succeed silently. Perfect for setting up directory structures for projects or ensuring required paths exist. Only works within allowed directories. 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.
create_directory accepts 1 parameter: path. Required: path. The full parameter table on this page comes from the server's own tool schema.
Register the Filesystem 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. 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 (@modelcontextprotocol/server-filesystem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Filesystem, and thousands of servers like it.
This server
Across the catalogue