batch_update_properties_tool
A write tool on the Obsidian MCP server.
This record as markdown: /tools/adrienthebo-obsidian-mcp/batch-update-properties-tool.md
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 batch_update_properties_tool is rated Medium
The tool performs batch updates to note properties, which are reversible modifications to data (Write category). Severity is high because batch operations at scale can affect many notes simultaneously, creating significant blast radius if misused by an AI agent (e.g., corrupting metadata across numerous vault files).
From the tool's definition Tool name 'batch_update_properties_tool' indicates batch modification of note properties. Combined with sibling tools like 'edit_note_section_tool' and 'create_note_tool' on an Obsidian vault system that provides 'direct filesystem access for reading,…
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs batch_update_properties_tool safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Obsidian MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For batch_update_properties_tool, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Obsidian MCP Server, apply this rule, and every batch_update_properties_tool call is checked against it from then on.
Questions about batch_update_properties_tool
batch_update_properties_tool is a write tool on the Obsidian MCP Server MCP server. 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.
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.
batch_update_properties_tool is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
batch_update_properties_tool is provided by the Obsidian MCP Server MCP server (adrienthebo/obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Obsidian MCP Server, and thousands of servers like it.
This server
Across the catalogue