Create a weekly review note from template
AI agents use weekly_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.
This tool creates a new note document (weekly review) based on a template. This is a reversible write operation with no side effects on external systems or financial implications. The blast radius is minimal—a mistaken weekly review note can be easily deleted. The operation is confined to the local Obsidian vault and follows standard note creation patterns consistent with the server's GTD/PARA planning methodology.
From the tool's definition Tool name contains 'create' and description states 'Create a weekly review note from template', which generates a new document in the Obsidian vault.
Attacks that exploit this kind of access
Create a weekly review note from template. 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 weekly_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.
weekly_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 weekly_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 weekly_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.
weekly_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 →