commit_title

Title for merge commit (string, optional)

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

Low RISK CLASS

Category Other

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-aifity-omnigit-mcp/commit-title.md

WHAT IT DOES

What commit_title does on GitHub

AI agents call commit_title as a supporting operation in GitHub workflows.

RISK

Why commit_title is rated Low

This does not appear to be a standalone executable tool but rather a parameter definition (a string input field for specifying a commit title). It has no actionable behavior of its own. Confidence is low due to the uninformative description that describes a parameter rather than a tool operation.

From the tool's definition Tool name is 'commit_title' and description says 'Title for merge commit (string, optional)' — this appears to be a parameter/field descriptor, not an actionable tool.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs commit_title 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 commit_title, this is the rule to start with:

commit_title Rate-limited

commit_title gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "commit_title": {
      "limits": [
        {
          "counter": "commit_title_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about commit_title

What does the commit_title tool do? +

Title for merge commit (string, optional). It is categorised as a Other tool in the GitHub MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on commit_title? +

Register the GitHub MCP server in PolicyLayer and add a rule for commit_title: 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 commit_title? +

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

Can I rate-limit commit_title? +

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

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

commit_title 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 →Tool risk categories →MCP tool →