create_directory
AI agents use create_directory to create or update resources in Tafa MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tafa MCP Server environment.
Creating a directory is a reversible write operation that modifies the file system by adding a new directory structure. It does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or merely read data (Read). While it has some side effects, directories can be removed, making it a Write-category operation.
From the tool's definition Tool named 'create_directory' is listed among file system management tools on a file operations MCP server alongside tools like 'copy_file', 'append_file', 'delete_file', etc.
Attacks that exploit this kind of access
create_directory. It is categorised as a Write tool in the Tafa MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tafa 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 Tafa 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 Tafa MCP Server MCP server (n3urax/tafa-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 →