obsidian_complete_task · Mcp Apple Obsidian MCP

WHAT IT DOES

What obsidian_complete_task does on Mcp Apple Obsidian

AI agents use obsidian_complete_task to create or update resources in Mcp Apple Obsidian — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Apple Obsidian environment.

WHY IT NEEDS A POLICY

Why obsidian_complete_task needs a policy

Marking a task as completed is a reversible state modification. While it changes data, it is not destructive (the task still exists, only its completion status changes) and does not execute arbitrary code or perform financial transactions.

From the tool's definition Tool description states 'Mark a task as completed' — this modifies task state in Obsidian notes. The sibling tools include obsidian_add_task, obsidian_delete_task, and obsidian_append_note, all of which are Write-category operations that alter vault content.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

obsidian_complete_task Rate-limited

obsidian_complete_task 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "obsidian_complete_task": {
      "limits": [
        {
          "counter": "obsidian_complete_task_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mcp Apple Obsidian, so you can run agents against it safely.

FAQ

Questions about obsidian_complete_task

What does the obsidian_complete_task tool do? +

Mark a task as completed by matching its description. It is categorised as a Write tool in the Mcp Apple Obsidian MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on obsidian_complete_task? +

Register the Mcp Apple Obsidian MCP server in PolicyLayer and add a rule for obsidian_complete_task: 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 Apple Obsidian. Nothing to install.

What risk level is obsidian_complete_task? +

obsidian_complete_task is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit obsidian_complete_task? +

Yes. Add a rate_limit block to the obsidian_complete_task 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.

How do I block obsidian_complete_task completely? +

Set action: deny in the PolicyLayer policy for obsidian_complete_task. 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.

What MCP server provides obsidian_complete_task? +

obsidian_complete_task is provided by the Mcp Apple Obsidian MCP server (rex/mcp-apple-obsidian). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.