Get file metadata (size, modification date). Returns exists: false if file not found.
AI agents call get_file_info to retrieve information from Obsidian HTTP MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves file system metadata only. It has no side effects, makes no modifications, and cannot cause data loss or unintended consequences. The worst case is information disclosure about file properties, which poses minimal risk even in an agentic context.
From the tool's definition Tool description states it 'Get[s] file metadata (size, modification date)' which are read-only queries. Returns information about file existence and properties without modifying, creating, or deleting any data.
Documented attack patterns abuse exactly the kind of access get_file_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian HTTP MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_file_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_file_info": {}
}
} get_file_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get file metadata (size, modification date). Returns exists: false if file not found. It is categorised as a Read tool in the Obsidian HTTP MCP MCP Server, which means it retrieves data without modifying state.
Register the Obsidian HTTP MCP server in PolicyLayer and add a rule for get_file_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 Obsidian HTTP MCP. Nothing to install.
get_file_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_file_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_file_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_file_info is provided by the Obsidian HTTP MCP server (nasandnora/obsidian-http-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Obsidian HTTP MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 Obsidian HTTP MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.