Open one or more files in the vault in a new leaf
AI agents invoke obsidian_open_files to trigger actions in Advanced Obsidian MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external UI operation in Obsidian (opening files in a new leaf/pane), which is an action that affects the application state rather than simply reading or writing data. It executes a command in the Obsidian interface. The blast radius is low since it only opens files for viewing and doesn't modify or delete any data.
From the tool's definition Open one or more files in the vault in a new leaf
Documented attack patterns abuse exactly the kind of access obsidian_open_files gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Advanced Obsidian MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for obsidian_open_files:
{
"version": "1",
"default": "deny",
"tools": {
"obsidian_open_files": {
"limits": [
{
"counter": "obsidian_open_files_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} obsidian_open_files stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Open one or more files in the vault in a new leaf. It is categorised as a Execute tool in the Advanced Obsidian MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Advanced Obsidian MCP Server MCP server in PolicyLayer and add a rule for obsidian_open_files: 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 Advanced Obsidian MCP Server. Nothing to install.
obsidian_open_files is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the obsidian_open_files 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 obsidian_open_files. 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.
obsidian_open_files is provided by the Advanced Obsidian MCP Server MCP server (tokidoo/mcp-obsidian-advanced). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Advanced 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.
16 Advanced Obsidian MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.