obsidian_rename_tag_vault · Mcp Apple Obsidian MCP

WHAT IT DOES

What obsidian_rename_tag_vault does on Mcp Apple Obsidian

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

WHY IT NEEDS A POLICY

Why obsidian_rename_tag_vault needs a policy

This tool modifies data (tag names) across multiple notes reversibly. While it affects many notes, renaming is not destructive since the original content remains and the operation can be undone (tags can be renamed back). It is Write rather than Execute because the operation is deterministic based on tag identity, not arbitrary code execution.

From the tool's definition Tool name contains 'rename' and description states it will 'Rename a tag across all notes in the vault' — this modifies metadata (tags) on potentially many notes simultaneously.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

obsidian_rename_tag_vault Rate-limited

obsidian_rename_tag_vault 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": {
    "obsidian_rename_tag_vault": {
      "limits": [
        {
          "counter": "obsidian_rename_tag_vault_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 Mcp Apple Obsidian, so you can run agents against it safely.

FAQ

Questions about obsidian_rename_tag_vault

What does the obsidian_rename_tag_vault tool do? +

Rename a tag across all notes in the vault. It is categorised as a Write tool in the Mcp Apple 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 obsidian_rename_tag_vault? +

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

What risk level is obsidian_rename_tag_vault? +

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

Can I rate-limit obsidian_rename_tag_vault? +

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

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

obsidian_rename_tag_vault is provided by the Mcp Apple Obsidian MCP server (rex/mcp-apple-obsidian). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.