AI agents use create_task_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.
This tool creates new notes in an Obsidian vault, which is a write operation that modifies the vault by adding content. It is reversible (notes can be deleted) and does not execute code, delete data irreversibly, or move money. The blast radius is low—a misused tool would only create unwanted task notes that can be easily removed.
From the tool's definition Tool is named 'create_task_note' and described as 'Create a dedicated task list note'. The verb 'create' indicates new data generation. The scope is limited to task list notes, which are reversible additions to the vault.
Documented attack patterns abuse exactly the kind of access create_task_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_task_note:
{
"version": "1",
"default": "deny",
"tools": {
"create_task_note": {
"limits": [
{
"counter": "create_task_note_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_task_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 dedicated task list note. 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_task_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_task_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_task_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_task_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_task_note is provided by the Obsidian MCP Server MCP server (kynlos/obsidian-mcp). 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.
120 Obsidian MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.