create_directory
Create a new directory or ensure a directory exists. Can create multiple nested directories in one operation. Only works within allowed directories. ${PATH_GUIDANCE} ${CMD_PREFIX_DESCRIPTION}
This record as markdown: /tools/desktop-commander/create-directory.md
What create_directory does on Desktop Commander
AI agents use create_directory to create or update resources in Desktop Commander, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Desktop Commander environment.
Why create_directory is rated Medium
Creating directories is a reversible modification to the filesystem. While not destructive (directories can be removed), it is not merely a read operation. The tool operates within allowed directories, which mitigates risk somewhat.
From the tool's definition Tool name is 'create_directory' and description states 'Create a new directory or ensure a directory exists.' This is a write operation that creates new data structures (directories) in the filesystem.
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 Desktop Commander, 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 Desktop Commander, 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. Only works within allowed directories. ${PATH_GUIDANCE} ${CMD_PREFIX_DESCRIPTION}. It is categorised as a Write tool in the Desktop Commander MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Desktop Commander 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 Desktop Commander. 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 Desktop Commander MCP server (wonderwhy-er/DesktopCommanderMCP). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Desktop Commander, and thousands of servers like it.
This server
Across the catalogue