List your most recent diary entries.
AI agents call list_recent_entries 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 queries and returns metadata about diary entries without altering, deleting, or executing any operations. It is a straightforward data retrieval function with no side effects, placing it firmly in the Read category. The severity is low because listing entries poses minimal risk—it only exposes information the user already has access to within their own Obsidian vault.
From the tool's definition Tool name 'list_recent_entries' and description 'List your most recent diary entries' indicate a retrieval operation with no modification, deletion, or execution of commands.
Attacks that exploit this kind of access
List your most recent diary entries. 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 list_recent_entries: 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.
list_recent_entries 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 list_recent_entries 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 list_recent_entries. 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.
list_recent_entries 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 →