Create a git checkpoint with a commit message
AI agents use git_checkpoint to create or update resources in Obsidian Ai Curator — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obsidian Ai Curator environment.
This tool creates a new commit in a git repository, which is a reversible write operation. While commits can technically be undone (via git reset, revert, etc.), they permanently alter version control history and could mislead collaborators or interfere with collaborative workflows. The medium severity reflects that commits are modifiable but their creation has side effects on repository state and team coordination.
From the tool's definition Tool creates a git checkpoint with a commit message, which modifies the repository's git history by creating a new commit.
Documented attack patterns abuse exactly the kind of access git_checkpoint 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_checkpoint:
{
"version": "1",
"default": "deny",
"tools": {
"git_checkpoint": {
"limits": [
{
"counter": "git_checkpoint_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}git_checkpoint 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.
Free to start. No card required.
Create a git checkpoint with a commit message. It is categorised as a Write tool in the Obsidian Ai Curator MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Obsidian Ai Curator MCP server in PolicyLayer and add a rule for git_checkpoint: 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_checkpoint 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 git_checkpoint 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_checkpoint. 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_checkpoint 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.