Batch operations for multiple notes at once. IMPORTANT: dry_run defaults to true - set dry_run: false to actually make changes. Delete operations require confirm: true in addition to dry_run: false. Selection methods: - glob: Match files by pattern (e.g.,
AI agents call palace_batch to permanently remove resources in Obsidian Palace MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool spans Write and Destructive categories. Because it supports batch delete operations on multiple notes at once, the most severe applicable category is Destructive. The blast radius is critical since a misconfigured batch delete could wipe out an entire vault or large portions of it irreversibly.
From the tool's definition 'Batch operations for multiple notes at once' combined with 'Delete operations require confirm: true in addition to dry_run: false' — the tool explicitly supports delete operations across multiple notes simultaneously, which is irreversible.
Attacks that exploit this kind of access
Batch operations for multiple notes at once. IMPORTANT: dry_run defaults to true - set dry_run: false to actually make changes. Delete operations require confirm: true in addition to dry_run: false. Selection methods: - glob: Match files by pattern (e.g.,. It is categorised as a Destructive tool in the Obsidian Palace MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Obsidian Palace MCP server in PolicyLayer and add a rule for palace_batch: 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 Palace MCP. Nothing to install.
palace_batch is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the palace_batch 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 palace_batch. 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.
palace_batch is provided by the Obsidian Palace MCP server (probably-computers/obsidian-palace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →