Get a daily note with parsed sections (focus, tasks, log, gratitude, reflection)
AI agents call daily_get to retrieve information from Mcp Obsidian Planner without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves structured data from a daily note without creating, modifying, deleting, or executing anything. It has no side effects beyond returning information. The blast radius of misuse is minimal—an AI agent could only over-retrieve notes, which causes no harm to the vault state.
From the tool's definition Tool retrieves and parses a daily note's existing sections (focus, tasks, log, gratitude, reflection). The verb 'Get' combined with 'parsed sections' indicates read-only retrieval of data with no modification, deletion, or execution.
Attacks that exploit this kind of access
Get a daily note with parsed sections (focus, tasks, log, gratitude, reflection). It is categorised as a Read tool in the Mcp Obsidian Planner MCP Server, which means it retrieves data without modifying state.
Register the Mcp Obsidian Planner MCP server in PolicyLayer and add a rule for daily_get: 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 Mcp Obsidian Planner. Nothing to install.
daily_get 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 daily_get 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 daily_get. 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.
daily_get is provided by the Mcp Obsidian Planner MCP server (jarero321/mcp-obsidian-planner). 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 →