Create a daily note from template. Returns existing note if already created.
AI agents use daily_create to create or update resources in Mcp Obsidian Planner — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Obsidian Planner environment.
The tool creates new daily notes in the Obsidian vault, which is a reversible write operation. It does not execute arbitrary code, delete data, or affect financial systems. The 'Returns existing note if already created' behavior indicates idempotency and no destructive side effects. Severity is low because creating templated notes in a personal planning system has minimal blast radius even if invoked unintentionally.
From the tool's definition Tool description states 'Create a daily note from template', which is a create operation that modifies the vault by adding new notes.
Attacks that exploit this kind of access
Create a daily note from template. Returns existing note if already created. It is categorised as a Write tool in the Mcp Obsidian Planner MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Obsidian Planner MCP server in PolicyLayer and add a rule for daily_create: 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_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the daily_create 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_create. 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_create 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 →