obsidian_rename_tag · Obsidian MCP: Risk & Policy

WHAT IT DOES

What obsidian_rename_tag does on Obsidian

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

WHY IT NEEDS A POLICY

Why obsidian_rename_tag needs a policy

The tool modifies tag data across the entire vault, affecting potentially hundreds or thousands of notes. While reversible (a rename can be undone), the blast radius is very large—an AI agent given incorrect tag parameters could rename important organizational tags to gibberish, causing significant disruption to vault structure and discoverability.

From the tool's definition Tool description: 'Renames a tag across every note in the vault.' The verb 'renames' indicates modification of data (frontmatter, tag references) across multiple notes. This is a write operation that modifies content reversibly.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

obsidian_rename_tag Rate-limited

obsidian_rename_tag 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": {
      "limits": [
        {
          "counter": "obsidian_rename_tag_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, so you can run agents against it safely.

FAQ

Questions about obsidian_rename_tag

What does the obsidian_rename_tag tool do? +

Renames a tag across every note in the vault. It is categorised as a Write tool in the 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? +

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

What risk level is obsidian_rename_tag? +

obsidian_rename_tag 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? +

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

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

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