max_count

Maximum number of commits to show (default: 10) (number, optional)

SERVERGitHub SOURCEoci:ghcr.io/aifity/omnigit-mcp:0.5.0

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-aifity-omnigit-mcp/max-count.md

WHAT IT DOES

What max_count does on GitHub

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

RISK

Why max_count is rated Low

This is a pagination/filtering parameter for controlling the number of results returned from a commit query operation. It has no side effects and does not modify any data. It only affects the scope of data displayed in a read operation, making it a low-severity read category tool.

From the tool's definition Tool name 'max_count' with description 'Maximum number of commits to show' indicates a parameter that limits query results. This is a read-only parameter used to control pagination/display of commit data, not to retrieve data directly.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs max_count safely

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

max_count Allowed

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

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

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

FAQ

Questions about max_count

What does the max_count tool do? +

Maximum number of commits to show (default: 10) (number, optional). It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on max_count? +

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

What risk level is max_count? +

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

Can I rate-limit max_count? +

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

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

max_count is provided by the GitHub MCP server (oci:ghcr.io/aifity/omnigit-mcp:0.5.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GitHub, and thousands of servers like it.

This server

All 245 GitHub tools →

Across the catalogue

The MCP Attack Database →

Guides

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