AI agents call fabric_git_compare_commits to retrieve information from Git Steer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only comparison operation between git references. It retrieves information about commit divergence and changed files but does not create, modify, delete, or execute any code. The action has no side effects on repositories, branches, or any other system state. This is a standard git inspection capability similar to 'git diff' or 'git log' commands.
From the tool's definition Tool description states 'Compare two refs to see divergence and changed files' - this is a query operation that retrieves and displays information about git commits and file changes without modifying any data.
Attacks that exploit this kind of access
[git-fabric] Compare two refs to see divergence and changed files. It is categorised as a Read tool in the Git Steer MCP Server, which means it retrieves data without modifying state.
Register the Git Steer MCP server in PolicyLayer and add a rule for fabric_git_compare_commits: 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 Git Steer. Nothing to install.
fabric_git_compare_commits 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 fabric_git_compare_commits 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 fabric_git_compare_commits. 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.
fabric_git_compare_commits is provided by the Git Steer MCP server (ry-ops/git-steer). 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 →