create_diary_entry_file · Obsidian Diary MCP Server MCP

WHAT IT DOES

What create_diary_entry_file does on Obsidian Diary MCP Server

AI agents use create_diary_entry_file 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 create_diary_entry_file needs a policy

This tool creates new diary entry files in Obsidian, which is a write operation that modifies the user's knowledge base by adding new content. While it generates AI prompts for reflection, the core function is creating and storing new data. It is not destructive (entries can be removed), not financial, and not execute-class (no arbitrary code execution or external commands triggered).

From the tool's definition Tool description explicitly states 'CREATE A NEW DIARY LOG ENTRY' indicating creation of new data/files. The action is reversible (files can be deleted, entries edited) and has no irreversible consequences.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_diary_entry_file Rate-limited

create_diary_entry_file 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": {
    "create_diary_entry_file": {
      "limits": [
        {
          "counter": "create_diary_entry_file_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 create_diary_entry_file

What does the create_diary_entry_file tool do? +

CREATE A NEW DIARY LOG ENTRY for a specific date with AI-generated analytical prompts for deep intellectual exploration. 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 create_diary_entry_file? +

Register the Obsidian Diary MCP Server MCP server in PolicyLayer and add a rule for create_diary_entry_file: 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 create_diary_entry_file? +

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

Can I rate-limit create_diary_entry_file? +

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

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

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