filesystem_create_dir
Create a directory (recursively) in the project filesystem, then rescan. No-op if it already exists.
This record as markdown: /tools/breakpoint-mcp/filesystem-create-dir.md
What filesystem_create_dir does on Breakpoint
AI agents use filesystem_create_dir to create or update resources in Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Breakpoint environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Directory res:// path to create |
Parameters from the server's own tool schema.
Why filesystem_create_dir is rated Medium
Creating directories is a Write operation—it modifies the filesystem state by adding new structures, but the action is reversible (directories can be deleted). The scope is limited to a 'project filesystem' and poses low severity risk since directory creation alone causes no destructive damage and can be easily undone. No data loss, financial impact, or code execution occurs.
From the tool's definition Tool name contains 'create' and description explicitly states 'Create a directory (recursively) in the project filesystem'. This is a reversible creation operation.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs filesystem_create_dir safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For filesystem_create_dir, this is the rule to start with:
filesystem_create_dir stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every filesystem_create_dir call is checked against it from then on.
Questions about filesystem_create_dir
Create a directory (recursively) in the project filesystem, then rescan. No-op if it already exists. It is categorised as a Write tool in the Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
filesystem_create_dir accepts 1 parameter: path. Required: path. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for filesystem_create_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 Breakpoint. Nothing to install.
filesystem_create_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 filesystem_create_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 filesystem_create_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.
filesystem_create_dir is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
This server
Across the catalogue