Read a specific diary entry by date.
AI agents call read_diary_entry to retrieve information from Obsidian Diary MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves an existing diary entry based on a date parameter. It performs a query operation that returns data without creating, modifying, deleting, or executing code. The only risk is potential exposure of personal diary content, which is inherent to the read operation itself and represents a low-severity information disclosure risk manageable through access controls.
From the tool's definition Tool name is 'read_diary_entry' and description states 'Read a specific diary entry by date.' The verb 'read' and the retrieval-focused purpose clearly indicate data retrieval without modification or side effects.
Attacks that exploit this kind of access
Read a specific diary entry by date. It is categorised as a Read tool in the Obsidian Diary MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Obsidian Diary MCP Server MCP server in PolicyLayer and add a rule for read_diary_entry: 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 Diary MCP Server. Nothing to install.
read_diary_entry 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 read_diary_entry 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 read_diary_entry. 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.
read_diary_entry is provided by the Obsidian Diary MCP Server MCP server (madebygps/obsidian-diary-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 →