AI agents use make_dir to create or update resources in Fs Git — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fs Git environment.
Creating a directory is a write operation that modifies the filesystem by adding a new directory. This operation is reversible (directories can be deleted). Given the server's design enforces git commits on writes, this action will be tracked and can be undone through git history. It does not delete data, execute arbitrary code, or commit financial transactions, making Write the appropriate category.
From the tool's definition Tool name 'make_dir' with description 'Create directory' indicates a directory creation operation, which is a write operation that creates data structures reversibly.
Attacks that exploit this kind of access
Create directory. It is categorised as a Write tool in the Fs Git MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fs Git MCP server in PolicyLayer and add a rule for make_dir: 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 Fs Git. Nothing to install.
make_dir 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 make_dir 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 make_dir. 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.
make_dir is provided by the Fs Git MCP server (wojons/fs-git-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 →