List all .base files in the vault.
AI agents call list_base_files 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 retrieves metadata about files in the vault without creating, modifying, deleting, or executing anything. It is a simple enumeration operation with no side effects. Low severity due to minimal blast radius—listing files poses no risk of data loss or corruption if called by an AI agent.
From the tool's definition Tool name 'list_base_files' and description 'List all .base files in the vault' indicate a query/retrieval operation with no modification or destructive capability.
Attacks that exploit this kind of access
List all .base files in the vault. 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_base_files: 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_base_files 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_base_files 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_base_files. 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_base_files 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.
list_base_files is one line of Graph Rag Obsidian's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →