get_vault_guide | PolicyLayer

WHAT IT DOES

What get_vault_guide does on Obsidian MCP (pgvector + Ollama, self-hosted)

AI agents call get_vault_guide to retrieve information from Obsidian MCP (pgvector + Ollama, self-hosted) without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

WHY IT NEEDS A POLICY

Why get_vault_guide needs a policy

The tool appears to retrieve or query guide/documentation data about the vault. No side effects, modifications, code execution, or destructive operations are implied. The empty description reduces confidence slightly, but context from sibling tools and server description strongly suggests this is informational retrieval.

From the tool's definition Tool name 'get_vault_guide' suggests retrieval of documentation or metadata. Sibling tools include read operations (get_backlinks, get_links, get_neighborhood, get_recent, get_tags) and the server description mentions 'self-describing vault guide', implying…

Attacks that exploit this kind of access

Questions about get_vault_guide

What does the get_vault_guide tool do? +

get_vault_guide. It is categorised as a Read tool in the Obsidian MCP (pgvector + Ollama, self-hosted) MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_vault_guide? +

Register the Obsidian MCP (pgvector + Ollama, self-hosted) MCP server in PolicyLayer and add a rule for get_vault_guide: 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 (pgvector + Ollama, self-hosted). Nothing to install.

What risk level is get_vault_guide? +

get_vault_guide is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_vault_guide? +

Yes. Add a rate_limit block to the get_vault_guide 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.

How do I block get_vault_guide completely? +

Set action: deny in the PolicyLayer policy for get_vault_guide. 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.

What MCP server provides get_vault_guide? +

get_vault_guide is provided by the Obsidian MCP (pgvector + Ollama, self-hosted) MCP server (maxkuminov/obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.