AI agents call git_changes to retrieve information from Obsidian Ai Curator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the git repository state (changed files, status, diff information) without creating, modifying, executing, or deleting anything. It is a read-only operation that retrieves information about the repository's current state. Even in the context of an Obsidian vault with file management capabilities, git_changes itself only inspects and reports status without side effects.
From the tool's definition Tool name 'git_changes' and description 'Get current git changes and status' indicate retrieval of git repository metadata and file status information with no modification or execution capabilities.
Documented attack patterns abuse exactly the kind of access git_changes 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_changes:
{
"version": "1",
"default": "deny",
"tools": {
"git_changes": {}
}
}git_changes is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get current git changes and status. It is categorised as a Read tool in the Obsidian Ai Curator MCP Server, which means it retrieves data without modifying state.
Register the Obsidian Ai Curator MCP server in PolicyLayer and add a rule for git_changes: 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_changes is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the git_changes 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_changes. 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_changes 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.