Add a new task to a note in the Tareas section
AI agents use task_add 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 task entry, which is a reversible write operation. It does not execute arbitrary code, delete data, move money, or trigger external operations with unpredictable effects. Severity is medium because an AI agent could add spurious or misleading tasks that clutter the task system, but the impact is bounded to the note structure and recoverable.
From the tool's definition Tool name 'task_add' and description 'Add a new task to a note in the Tareas section' indicate creation of new data without deletion or modification of existing records.
Attacks that exploit this kind of access
Add a new task to a note in the Tareas section. 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 task_add: 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.
task_add 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 task_add 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 task_add. 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.
task_add 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 →