github_list_commits

List commits for a repository

SERVERScopeGate SOURCEhttps://mcp.scopegate.cloud/{api_key}

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/io-github-alifanov-scopegate/github-list-commits.md

WHAT IT DOES

What github_list_commits does on ScopeGate

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

RISK

Why github_list_commits is rated Low

This tool retrieves historical commit information from a repository. It performs a read-only query operation with no side effects, no code execution, and no data modification or deletion. The blast radius of misuse is minimal—an agent could retrieve unwanted commit history but cannot alter repositories, execute code, or cause financial impact.

From the tool's definition Tool name includes 'list' and description states 'List commits for a repository', indicating data retrieval without modification or execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs github_list_commits safely

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

github_list_commits Allowed

github_list_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": {
    "github_list_commits": {}
  }
}

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

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

FAQ

Questions about github_list_commits

What does the github_list_commits tool do? +

List commits for a repository. It is categorised as a Read tool in the ScopeGate MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on github_list_commits? +

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

What risk level is github_list_commits? +

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

Can I rate-limit github_list_commits? +

Yes. Add a rate_limit block to the github_list_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 github_list_commits completely? +

Set action: deny in the PolicyLayer policy for github_list_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 github_list_commits? +

github_list_commits is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ScopeGate, and thousands of servers like it.

This server

All 385 ScopeGate tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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