List all .base files in the vault with their metadata.
AI agents call list_bases to retrieve information from Graph Rag Obsidian without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query operation that retrieves and enumerates existing .base files along with their metadata. It has no side effects—no data is created, modified, deleted, or executed. The operation is purely informational, making it a Read category tool with low severity since it merely provides visibility into local vault structure.
From the tool's definition Tool name 'list_bases' and description 'List all .base files in the vault with their metadata' indicate retrieval of data without modification or deletion.
Attacks that exploit this kind of access
List all .base files in the vault with their metadata. It is categorised as a Read tool in the Graph Rag Obsidian MCP Server, which means it retrieves data without modifying state.
Register the Graph Rag Obsidian MCP server in PolicyLayer and add a rule for list_bases: 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 Graph Rag Obsidian. Nothing to install.
list_bases 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_bases 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_bases. 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_bases is provided by the Graph Rag Obsidian MCP server (nickshffer/graph-rag-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 →