AI agents call obsidian-mcp-rollback-edit to permanently remove resources in Vault MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The name 'rollback-edit' suggests reverting or undoing a previous edit, which overwrites current file state with a prior version. In the context of an Obsidian vault file management server, this likely irreversibly discards the current version of a file.
From the tool's definition Tool name: obsidian-mcp-rollback-edit; description is empty
Documented attack patterns abuse exactly the kind of access obsidian-mcp-rollback-edit gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Vault MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for obsidian-mcp-rollback-edit:
{
"version": "1",
"default": "deny",
"hide": [
"obsidian-mcp-rollback-edit"
]
}obsidian-mcp-rollback-edit disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
obsidian-mcp-rollback-edit. It is categorised as a Destructive tool in the Vault MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Vault MCP server in PolicyLayer and add a rule for obsidian-mcp-rollback-edit: 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 Vault MCP. Nothing to install.
obsidian-mcp-rollback-edit 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 obsidian-mcp-rollback-edit 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 obsidian-mcp-rollback-edit. 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.
obsidian-mcp-rollback-edit is provided by the Vault MCP server (jlevere/obsidian-mcp-plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Vault MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Vault MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.