list_folders_tool
AI agents call list_folders_tool 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 appears to query and retrieve folder information from the Obsidian vault filesystem. Listing folders has no side effects, creates no data modifications, and cannot damage or delete information. It is a straightforward Read operation with low blast radius if misused by an AI agent—at worst, it would expose vault structure information.
From the tool's definition Tool name 'list_folders_tool' indicates a listing/enumeration operation. No description provided, but naming convention strongly suggests it retrieves folder structure without modification.
Attacks that exploit this kind of access
list_folders_tool. 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 list_folders_tool: 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.
list_folders_tool 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_folders_tool 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_folders_tool. 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_folders_tool is provided by the Obsidian MCP Server MCP server (suhailnajeeb/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 →