List all configured vaults with their aliases, paths, access modes, and optionally note counts.
AI agents call palace_vaults to retrieve information from Obsidian Palace MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing configuration data. It has no side effects, does not execute code, does not modify or delete data, and does not move resources. It is a pure information retrieval operation, fitting the Read category. Severity is low because exposure of vault metadata poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'palace_vaults' with description 'List all configured vaults' — a read-only operation that retrieves vault metadata (aliases, paths, access modes, note counts) without modification or execution.
Attacks that exploit this kind of access
List all configured vaults with their aliases, paths, access modes, and optionally note counts. It is categorised as a Read tool in the Obsidian Palace MCP MCP Server, which means it retrieves data without modifying state.
Register the Obsidian Palace MCP server in PolicyLayer and add a rule for palace_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 Palace MCP. Nothing to install.
palace_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 palace_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 palace_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.
palace_vaults is provided by the Obsidian Palace MCP server (probably-computers/obsidian-palace-mcp). 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 →