Low Risk

list_commits

Get list of commits of a branch in a GitHub repository

How to control list_commits ↓

What list_commits does on GitHub MCP Server Plus

AI agents call list_commits to retrieve information from GitHub MCP Server Plus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why list_commits needs a policy

This tool queries and retrieves commit history data from a GitHub repository without creating, modifying, or deleting any resources. It has no side effects and poses minimal risk if called by an AI agent, as it only exposes existing historical information about commits. The blast radius is limited to potential exposure of repository history, which is typically intended to be discoverable.

From the tool's definition Tool name 'list_commits' and description 'Get list of commits of a branch in a GitHub repository' indicate a retrieval operation with no modification capability. The verb 'Get list' and 'list' prefix are characteristic of Read operations.

Documented attack patterns abuse exactly the kind of access list_commits gives an agent:

How to control list_commits

PolicyLayer is an MCP gateway — it sits between your AI agents and GitHub MCP Server Plus, and nothing reaches the server without passing your rules. This is the rule we recommend for list_commits:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_commits": {}
  }
}

list_commits is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register GitHub MCP Server Plus — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about list_commits

What does the list_commits tool do? +

Get list of commits of a branch in a GitHub repository. It is categorised as a Read tool in the GitHub MCP Server Plus MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_commits? +

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

What risk level is list_commits? +

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

Can I rate-limit list_commits? +

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

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

list_commits is provided by the GitHub MCP Server Plus MCP server (phialsbasement/mcp-github-server-plus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every GitHub MCP Server Plus tool call.

Start from GitHub MCP Server Plus, 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.

18 GitHub MCP Server Plus tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.