Get information about a specific vault
AI agents call get_vault_info to retrieve information from Obsidian MCP Server 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 vault information with no side effects. It fits the Read category definition: retrieves or queries data with no side effects. The low severity reflects minimal blast radius—an AI agent misusing this tool could only gather information about vault structure/metadata, posing no destructive, financial, or execution risks.
From the tool's definition Tool name 'get_vault_info' and description 'Get information about a specific vault' indicate a pure query operation that retrieves vault metadata without modifying, deleting, or executing any operations.
Attacks that exploit this kind of access
Get information about a specific vault. It is categorised as a Read tool in the Obsidian MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Obsidian MCP Server MCP server in PolicyLayer and add a rule for get_vault_info: 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 Server. Nothing to install.
get_vault_info 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_info 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_info. 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_info is provided by the Obsidian MCP Server MCP server (victors081/obsidian-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 →