commit_message
Extra detail for merge commit (string, optional)
This record as markdown: /tools/io-github-aifity-omnigit-mcp/commit-message.md
What commit_message does on GitHub
AI agents use commit_message to create or update resources in GitHub, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub environment.
Why commit_message is rated Medium
This tool creates a new commit message object, which is a reversible write operation. It does not delete data (Destructive), execute arbitrary code (Execute), or transfer funds (Financial). While merge commits modify the repository state, they are version-controlled and can be reverted, making this a Write rather than Destructive action.
From the tool's definition Tool modifies git history by creating a merge commit with a custom commit message. The description 'Extra detail for merge commit' indicates it creates or records new data (the commit message) as part of a merge operation.
Attacks that exploit this kind of access
The rule that runs commit_message 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_message, this is the rule to start with:
commit_message stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every commit_message call is checked against it from then on.
Questions about commit_message
Extra detail for merge commit (string, optional). It is categorised as a Write tool in the GitHub MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GitHub MCP server in PolicyLayer and add a rule for commit_message: 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.
commit_message is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the commit_message 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.
Set action: deny in the PolicyLayer policy for commit_message. 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.
commit_message 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.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue