Create a new directory, including parent directories if needed.
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 directories is a reversible filesystem modification that creates new data structures. It does not irreversibly delete data (would be Destructive), nor does it execute arbitrary code (would be Execute). While it modifies the filesystem, it is categorized as Write rather than higher severity because directory creation can be undone by deletion.
From the tool's definition Tool description states 'Create a new directory' which is a write operation that modifies filesystem state. The server description confirms it provides 'write' capabilities including 'create' operations.
Attacks that exploit this kind of access
Create a new directory, including parent directories if needed. 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 (njbrake/filesystem-mcp-server). 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 →