update_base · Graph Rag Obsidian MCP: Risk & Policy

WHAT IT DOES

What update_base does on Graph Rag Obsidian

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

WHY IT NEEDS A POLICY

Why update_base needs a policy

This tool modifies existing configuration files (.base files) but does not delete them or execute arbitrary code. The update operation is reversible—configurations can be changed back to previous states. While it could affect system behavior if malicious configurations are written, the impact is limited to configuration state rather than code execution or data destruction.

From the tool's definition Tool name 'update_base' combined with description 'Update an existing .base file configuration' indicates modification of existing configuration data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_base Rate-limited

update_base 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": {
    "update_base": {
      "limits": [
        {
          "counter": "update_base_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 Graph Rag Obsidian, so you can run agents against it safely.

FAQ

Questions about update_base

What does the update_base tool do? +

Update an existing .base file configuration. It is categorised as a Write tool in the Graph Rag Obsidian MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_base? +

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

What risk level is update_base? +

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

Can I rate-limit update_base? +

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

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

update_base is provided by the Graph Rag Obsidian MCP server (nickshffer/graph-rag-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.