open_graph · Obsidian MCP Server MCP: Risk & Policy

WHAT IT DOES

What open_graph does on Obsidian MCP Server

AI agents invoke open_graph to trigger actions in Obsidian MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why open_graph needs a policy

This tool triggers a UI action in Obsidian (opening the graph view), which is an external operation whose effect is executing a command in the application. It does not read, write, or delete data, but it does trigger an external operation. The severity is low because it merely changes the UI state with no data modification or destruction.

From the tool's definition 'Open graph view in Obsidian' - triggers an external UI operation in the Obsidian application

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

open_graph Rate-limited

open_graph stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "open_graph": {
      "limits": [
        {
          "counter": "open_graph_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 MCP Server, so you can run agents against it safely.

FAQ

Questions about open_graph

What does the open_graph tool do? +

Open graph view in Obsidian (requires REST API plugin). It is categorised as a Execute tool in the Obsidian MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on open_graph? +

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

What risk level is open_graph? +

open_graph is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit open_graph? +

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

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

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