Get detailed information about a specific folder
AI agents call get_folder_info to retrieve information from ObsidianReaderMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query of folder metadata without creating, modifying, deleting, or executing any operations. The verb 'get' and function name clearly indicate data retrieval with no side effects. Low severity because exposure of folder information poses minimal risk compared to destructive or execute operations.
From the tool's definition get_folder_info retrieves detailed information about a specific folder with no modification capability; aligns with retrieval operations like list_folders, list_notes, and get_note present on the server.
Attacks that exploit this kind of access
Get detailed information about a specific folder. It is categorised as a Read tool in the ObsidianReaderMCP MCP Server, which means it retrieves data without modifying state.
Register the ObsidianReader MCP server in PolicyLayer and add a rule for get_folder_info: 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 ObsidianReaderMCP. Nothing to install.
get_folder_info 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 get_folder_info 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 get_folder_info. 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.
get_folder_info is provided by the ObsidianReader MCP server (qianjue-cn/obsidianreadermcp). 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 →