Create a folder in the vault. Creates all intermediate folders in the path (like mkdir -p).
AI agents use create_folder to create or update resources in Obsidian Vault MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obsidian Vault MCP Server environment.
This tool creates new folder structures in the vault. While creation is reversible (folders can be deleted via the sibling delete_folder tool), it modifies the vault state. It does not execute arbitrary code, delete data irreversibly, or handle financial transactions.
From the tool's definition Tool description explicitly states "Create a folder in the vault" — a data modification operation. The context mentions the server enables "write" operations on Obsidian vault notes. Creating directories is a reversible write action.
Attacks that exploit this kind of access
Create a folder in the vault. Creates all intermediate folders in the path (like mkdir -p). It is categorised as a Write tool in the Obsidian Vault MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Obsidian Vault MCP Server MCP server in PolicyLayer and add a rule for create_folder: 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 Obsidian Vault MCP Server. Nothing to install.
create_folder 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_folder 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_folder. 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_folder is provided by the Obsidian Vault MCP Server MCP server (jonhollander/obsidian-mcp-cloudflare). 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 →