List all configured Obsidian vaults with their IDs and capabilities.
AI agents call list_vaults 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 information discovery by enumerating vault configurations and their capabilities. It has no ability to modify, delete, or execute operations. The blast radius of misuse is minimal — an AI agent could learn which vaults exist and their properties, but cannot act upon that information without using other tools. This is a straightforward Read category operation.
From the tool's definition Tool name is 'list_vaults' and description states it 'List all configured Obsidian vaults' — a pure query operation that retrieves vault metadata with no side effects or modifications.
Attacks that exploit this kind of access
List all configured Obsidian vaults with their IDs and capabilities. 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 list_vaults: 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.
list_vaults 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 list_vaults 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 list_vaults. 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.
list_vaults 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 →