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...
AI agents use create_directory to create or update resources in FilesystemMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FilesystemMCP environment.
This tool creates new filesystem structures (directories), which is a write operation that modifies the filesystem state. It is reversible (unlike destructive deletion), does not execute arbitrary code, and does not move money. The severity is low because directory creation has minimal impact—the worst case is cluttering the filesystem with unwanted empty directories, which can be cleaned up.
From the tool's definition Tool description states it "Create[s] a new directory" and "can create multiple nested directories in one operation." The name "create_directory" and verb "create" explicitly indicate data creation.
Attacks that exploit this kind of access
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 FilesystemMCP 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_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 FilesystemMCP. 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 (rijadalisic/filesystemmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →