Get the currently active file in Obsidian (requires REST API plugin)
AI agents call get_active_file 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 queries the state of Obsidian to determine which file is currently open/active. It performs no side effects, creates no data modifications, and triggers no external operations. It is a simple informational read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'get_active_file' and description 'Get the currently active file in Obsidian' indicate a retrieval operation that returns information about the current file without modifying any data.
Attacks that exploit this kind of access
Get the currently active file in Obsidian (requires REST API plugin). 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 get_active_file: 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.
get_active_file 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_active_file 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_active_file. 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_active_file is provided by the Obsidian MCP Server MCP server (victors081/obsidian-mcp-server). 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 →