list_files
AI agents call list_files 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.
'list_files' retrieves or queries directory/file information without side effects. Although the description is empty, the name and context strongly indicate a read-only operation consistent with other data retrieval tools on this Obsidian vault server. Even if misused by an agent, listing files presents minimal risk compared to create/edit/delete operations available on the same server.
From the tool's definition Tool name 'list_files' performs a listing/enumeration operation. Sibling tools on the server include clear read operations (get_backlinks, get_links, get_neighborhood, get_recent, get_tags) and destructive operations (delete_note), confirming this server…
Attacks that exploit this kind of access
list_files. 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.
Register the Obsidian MCP (pgvector + Ollama, self-hosted) MCP server in PolicyLayer and add a rule for list_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 Obsidian MCP (pgvector + Ollama, self-hosted). Nothing to install.
list_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_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_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_files 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.
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 →