gitlab_list_commits

List repository commits

SERVERSage MCP SOURCEsagemcp/sagemcp

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/sagemcp-sagemcp/gitlab-list-commits.md

WHAT IT DOES

What gitlab_list_commits does on Sage MCP

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

RISK

Why gitlab_list_commits is rated Low

This tool queries and returns a list of commits from a GitLab repository. It performs no modifications, deletions, or external operations—purely data retrieval. The blast radius of misuse is minimal; an agent could only access commit history metadata that is typically visible to authorized users. This is a standard Read operation.

From the tool's definition Tool name 'gitlab_list_commits' and description 'List repository commits' indicate a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gitlab_list_commits safely

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

gitlab_list_commits Allowed

gitlab_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": {
    "gitlab_list_commits": {}
  }
}

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

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

FAQ

Questions about gitlab_list_commits

What does the gitlab_list_commits tool do? +

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

How do I enforce a policy on gitlab_list_commits? +

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

What risk level is gitlab_list_commits? +

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

Can I rate-limit gitlab_list_commits? +

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

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

gitlab_list_commits is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage tools →

Across the catalogue

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

Guides

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