AI agents use create_yearly_note to create or update resources in Obsidian MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obsidian MCP Server environment.
The tool creates a new note object in the vault, which is a reversible modification of vault state. While this modifies the user's knowledge base, the impact is localized to note creation, affecting vault structure and content but not causing permanent loss. Medium severity reflects that AI agents could spam-create notes or clutter vaults, but harm is contained and undoable.
From the tool's definition Tool name 'create_yearly_note' and description 'Create a yearly note for a specific year' indicate creation of new data within the Obsidian vault. This is reversible (notes can be deleted), placing it in Write rather than Destructive.
Documented attack patterns abuse exactly the kind of access create_yearly_note gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_yearly_note:
{
"version": "1",
"default": "deny",
"tools": {
"create_yearly_note": {
"limits": [
{
"counter": "create_yearly_note_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_yearly_note stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a yearly note for a specific year. It is categorised as a Write tool in the Obsidian MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Obsidian MCP Server MCP server in PolicyLayer and add a rule for create_yearly_note: 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 Server. Nothing to install.
create_yearly_note 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 create_yearly_note 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 create_yearly_note. 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.
create_yearly_note is provided by the Obsidian MCP Server MCP server (bazylhorsey/obsidian-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Obsidian MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
29 Obsidian MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.