batch_update_properties_tool · Obsidian MCP Server MCP

WHAT IT DOES

What batch_update_properties_tool does on Obsidian MCP Server

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

WHY IT NEEDS A POLICY

Why batch_update_properties_tool needs a policy

This tool performs batch updates to note metadata/properties, which are reversible modifications (Write category). Severity is high due to blast radius: batch operations can modify many notes at once, potentially corrupting vault structure or destroying important metadata.

From the tool's definition Tool name 'batch_update_properties_tool' indicates bulk modification of note properties. Sibling context shows this server manages Obsidian vaults with direct filesystem access, supporting 'bulk operations' per server description.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

batch_update_properties_tool Rate-limited

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

FAQ

Questions about batch_update_properties_tool

What does the batch_update_properties_tool tool do? +

batch_update_properties_tool. It is categorised as a Write tool in the Obsidian 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 batch_update_properties_tool? +

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

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

Can I rate-limit batch_update_properties_tool? +

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

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

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