Create a new directory (requires write permission)
AI agents use create_directory to create or update resources in MCP File Operations Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP File Operations Server environment.
Creating a directory is a reversible write operation that modifies file system state. It does not delete data (Destructive), execute arbitrary code (Execute), or involve financial transactions (Financial). While write operations can have side effects if a directory name conflicts with important system paths, this is a standard file system write operation.
From the tool's definition Tool name 'create_directory' and description 'Create a new directory' indicate file system modification. The parenthetical '(requires write permission)' confirms write-level access is needed.
Attacks that exploit this kind of access
Create a new directory (requires write permission). It is categorised as a Write tool in the MCP File Operations Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP File Operations 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 MCP File Operations 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 MCP File Operations Server MCP server (kavishankarks/mcp). 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 →