AI agents call git_rollback to permanently remove resources in Obsidian Ai Curator — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Rolling back to a previous git commit overwrites the current state of the repository, effectively discarding all commits made after the target commit. This is an irreversible operation in the sense that uncommitted or non-backed-up changes are permanently lost, and it can affect the entire Obsidian vault's history.
From the tool's definition Rollback to a previous git commit
Documented attack patterns abuse exactly the kind of access git_rollback gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian Ai Curator, and nothing reaches the server without passing your rules. This is the rule we recommend for git_rollback:
{
"version": "1",
"default": "deny",
"hide": [
"git_rollback"
]
}git_rollback 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.
Rollback to a previous git commit. It is categorised as a Destructive tool in the Obsidian Ai Curator MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Obsidian Ai Curator MCP server in PolicyLayer and add a rule for git_rollback: 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 Ai Curator. Nothing to install.
git_rollback 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 git_rollback 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 git_rollback. 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.
git_rollback is provided by the Obsidian Ai Curator MCP server (nwant/obsidian-ai-curator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Obsidian Ai Curator, 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.
27 Obsidian Ai Curator tools catalogued and risk-classified — across an index of 43,000+ MCP servers.