Create a new vault (folder) for organizing notes
AI agents use create_vault to create or update resources in Obsidian MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obsidian MCP Server environment.
Creating a new vault is a write operation that establishes persistent data structures (folders) in the file system. While reversible via deletion, it modifies the vault organization state and could interfere with legitimate knowledge base structure if invoked incorrectly by an agent. Not destructive since vaults can be deleted, not execute since no code/commands run, not financial.
From the tool's definition create_vault - 'Create a new vault (folder) for organizing notes'. This operation creates a new directory structure within the Obsidian vault system.
Documented attack patterns abuse exactly the kind of access create_vault gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_vault:
{
"version": "1",
"default": "deny",
"tools": {
"create_vault": {
"limits": [
{
"counter": "create_vault_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_vault 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.
Free to start. No card required.
Create a new vault (folder) for organizing notes. It is categorised as a Write tool in the Obsidian MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Obsidian MCP Server MCP server in PolicyLayer and add a rule for create_vault: 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 MCP Server. Nothing to install.
create_vault 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_vault 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_vault. 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_vault is provided by the Obsidian MCP Server MCP server (kynlos/obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Obsidian MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
120 Obsidian MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.