Get the folder tree structure of the vault.
AI agents call get_vault_structure to retrieve information from Obsidian Modified without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a passive query of vault metadata to return structural information (folder hierarchy). It has no side effects, does not execute code or commands, does not modify data, and does not delete or create resources. The operation is purely informational, making it a straightforward Read category with low severity risk even if misused by an agent.
From the tool's definition Tool name 'get_vault_structure' and description 'Get the folder tree structure of the vault' indicate a read-only operation that retrieves hierarchical information about the vault's organization without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Get the folder tree structure of the vault. It is categorised as a Read tool in the Obsidian Modified MCP Server, which means it retrieves data without modifying state.
Register the Obsidian Modified MCP server in PolicyLayer and add a rule for get_vault_structure: 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 Modified. Nothing to install.
get_vault_structure is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_vault_structure 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 get_vault_structure. 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.
get_vault_structure is provided by the Obsidian Modified MCP server (@marwansaab/obsidian-modified-mcp-server). 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 →