MCP Tool: Reads the full content of a specific note file.
AI agents call get_note_content to retrieve information from Obsidian MCP Tool Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves data from an Obsidian vault without modifying, deleting, or executing any operations. It is purely informational and fits the Read category definition: 'retrieves or queries data; no side effects'. The severity is low because reading note content poses minimal risk even if misused by an AI agent—it cannot alter data, execute code, or cause destructive changes.
From the tool's definition Tool name 'get_note_content' and description 'Reads the full content of a specific note file' explicitly indicate a read-only operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_note_content gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian MCP Tool Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_note_content:
{
"version": "1",
"default": "deny",
"tools": {
"get_note_content": {}
}
}get_note_content 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.
MCP Tool: Reads the full content of a specific note file. It is categorised as a Read tool in the Obsidian MCP Tool Server MCP Server, which means it retrieves data without modifying state.
Register the Obsidian MCP Tool Server MCP server in PolicyLayer and add a rule for get_note_content: 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 Tool Server. Nothing to install.
get_note_content 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_note_content 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_note_content. 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_note_content is provided by the Obsidian MCP Tool Server MCP server (rwb3n/obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 18 Obsidian MCP Tool Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
18 Obsidian MCP Tool Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.