compare_commits

Compare two branches, tags, or commits

SERVERForgejo SOURCEsqcows/forgejo-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sqcows-forgejo-mcp/compare-commits.md

WHAT IT DOES

What compare_commits does on Forgejo

AI agents call compare_commits to retrieve information from Forgejo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why compare_commits is rated Low

Tool retrieves and displays differences between commits without modifying any repository data.

From the tool's definition Compare two branches, tags, or commits

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs compare_commits safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Forgejo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For compare_commits, this is the rule to start with:

compare_commits Allowed

compare_commits is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "compare_commits": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Forgejo, apply this rule, and every compare_commits call is checked against it from then on.

FAQ

Questions about compare_commits

What does the compare_commits tool do? +

Compare two branches, tags, or commits. It is categorised as a Read tool in the Forgejo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on compare_commits? +

Register the Forgejo MCP server in PolicyLayer and add a rule for 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 Forgejo. Nothing to install.

What risk level is compare_commits? +

compare_commits is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit compare_commits? +

Yes. Add a rate_limit block to the 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.

How do I block compare_commits completely? +

Set action: deny in the PolicyLayer policy for 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.

What MCP server provides compare_commits? +

compare_commits is provided by the Forgejo MCP server (sqcows/forgejo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Forgejo, and thousands of servers like it.

This server

All 457 Forgejo tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →