Critical Risk →

manage_folder

Create, rename, move, or delete a folder in the Obsidian vault

How to control manage_folder ↓

AI agents call manage_folder to permanently remove resources in Obsidian MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

The tool explicitly supports deleting folders, which is irreversible and could destroy entire subtrees of notes. Even rename/move operations on folders can have cascading effects on note links and organization. The most severe applicable category is Destructive due to the delete capability, and severity is high because misuse could wipe out entire folder hierarchies containing many notes.

From the tool's definition Create, rename, move, or delete a folder in the Obsidian vault

Documented attack patterns abuse exactly the kind of access manage_folder gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for manage_folder:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "manage_folder"
  ]
}

manage_folder disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Obsidian MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the manage_folder tool do? +

Create, rename, move, or delete a folder in the Obsidian vault. It is categorised as a Destructive tool in the Obsidian MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on manage_folder? +

Register the Obsidian MCP server in PolicyLayer and add a rule for manage_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 MCP. Nothing to install.

What risk level is manage_folder? +

manage_folder is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit manage_folder? +

Yes. Add a rate_limit block to the manage_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.

How do I block manage_folder completely? +

Set action: deny in the PolicyLayer policy for manage_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.

What MCP server provides manage_folder? +

manage_folder is provided by the Obsidian MCP server (newtype-01/obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Obsidian MCP tool call.

Deterministic rules across all 11 Obsidian MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

11 Obsidian MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.