append_entry · Obsidian Dictionary MCP Server MCP

WHAT IT DOES

What append_entry does on Obsidian Dictionary MCP Server

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

WHY IT NEEDS A POLICY

Why append_entry needs a policy

The tool creates new entries in a glossary file, which is a reversible write operation. It does not execute code, delete data, or affect financial systems. The severity is medium rather than low because uncontrolled appends could pollute the glossary with incorrect or malicious terminology definitions, though the impact is limited to a single knowledge base file rather than critical infrastructure.

From the tool's definition Tool description states 'Append a new glossary entry to the dictionary file' and 'add new technical terms to the Obsidian glossary' — these are create/modify operations on data stored in the vault.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

append_entry Rate-limited

append_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": {
    "append_entry": {
      "limits": [
        {
          "counter": "append_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 Dictionary MCP Server, so you can run agents against it safely.

FAQ

Questions about append_entry

What does the append_entry tool do? +

Append a new glossary entry to the dictionary file. Use this to add new technical terms to the Obsidian glossary. It is categorised as a Write tool in the Obsidian Dictionary 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 append_entry? +

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

What risk level is append_entry? +

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

Can I rate-limit append_entry? +

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

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

append_entry is provided by the Obsidian Dictionary MCP Server MCP server (sarahan774/obsidian-dictionary-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.