complete_diary_entry · Obsidian Diary MCP Server MCP

WHAT IT DOES

What complete_diary_entry does on Obsidian Diary MCP Server

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

WHY IT NEEDS A POLICY

Why complete_diary_entry needs a policy

This tool modifies diary entry content by completing it and generating memory links. While it does not delete data (ruling out Destructive) or execute arbitrary code (ruling out Execute), it creates or modifies journal entries in Obsidian, fitting the Write category.

From the tool's definition Tool name 'complete_diary_entry' and description 'automatically generates Obsidian-compatible memory links' indicates modification/completion of existing diary entry data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

complete_diary_entry Rate-limited

complete_diary_entry 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": {
    "complete_diary_entry": {
      "limits": [
        {
          "counter": "complete_diary_entry_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 Obsidian Diary MCP Server, so you can run agents against it safely.

FAQ

Questions about complete_diary_entry

What does the complete_diary_entry tool do? +

Complete your diary entry - automatically generates Obsidian-compatible memory links and provides cognitive analysis. It is categorised as a Write tool in the Obsidian Diary MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on complete_diary_entry? +

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

What risk level is complete_diary_entry? +

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

Can I rate-limit complete_diary_entry? +

Yes. Add a rate_limit block to the complete_diary_entry 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 complete_diary_entry completely? +

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

complete_diary_entry is provided by the Obsidian Diary MCP Server MCP server (madebygps/obsidian-diary-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.