AI agents call obsidian_files_with_tag to retrieve information from Obsidian without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns data (notes matching a tag filter) without creating, modifying, deleting, or executing any code. It is a pure read operation with minimal blast radius; misuse would only result in unauthorized information disclosure, not data destruction or external effects.
From the tool's definition Tool description states 'Lists every note tagged with the given tag' - a retrieval operation with no modification or side effects.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Lists every note tagged with the given tag. It is categorised as a Read tool in the Obsidian MCP Server, which means it retrieves data without modifying state.
Register the Obsidian MCP server in PolicyLayer and add a rule for obsidian_files_with_tag: 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. Nothing to install.
obsidian_files_with_tag 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 obsidian_files_with_tag 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 obsidian_files_with_tag. 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.
obsidian_files_with_tag is provided by the Obsidian MCP server (yuchi-chang/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 →