Return git diff for the workspace when it is a git repository.
AI agents call repo.git_diff to retrieve information from ForLoop MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and returns the git diff output — it queries the current state of the repository without modifying, executing, or deleting anything. It is a pure read operation with minimal blast radius.
From the tool's definition Return git diff for the workspace when it is a git repository
Attacks that exploit this kind of access
Return git diff for the workspace when it is a git repository. It is categorised as a Read tool in the ForLoop MCP MCP Server, which means it retrieves data without modifying state.
Register the ForLoop MCP server in PolicyLayer and add a rule for repo.git_diff: 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 ForLoop MCP. Nothing to install.
repo.git_diff 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 repo.git_diff 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 repo.git_diff. 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.
repo.git_diff is provided by the ForLoop MCP server (master0ffate/forloop-mcp). 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 →