refresh_recent_backlinks · Obsidian Diary MCP Server MCP

WHAT IT DOES

What refresh_recent_backlinks does on Obsidian Diary MCP Server

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

This tool modifies backlink metadata in diary entries, which is a reversible write operation. It does not delete data (not Destructive), does not execute arbitrary code (not Execute), and does not involve financial transactions (not Financial).

From the tool's definition Tool name 'refresh_recent_backlinks' and description 'Update backlinks for recent diary entries' indicate modification of existing diary entry metadata (backlinks).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

refresh_recent_backlinks Rate-limited

refresh_recent_backlinks 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": {
    "refresh_recent_backlinks": {
      "limits": [
        {
          "counter": "refresh_recent_backlinks_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 refresh_recent_backlinks

What does the refresh_recent_backlinks tool do? +

Update backlinks for recent diary entries only - much faster than full refresh. 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 refresh_recent_backlinks? +

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

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

Can I rate-limit refresh_recent_backlinks? +

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

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

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