Create a git commit
AI agents use git_commit to create or update resources in Coding MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Coding MCP Server environment.
git_commit creates a new commit object and updates the HEAD reference, modifying repository history in a way that can be undone. While commits are permanent in one sense, Git provides standard mechanisms to revert or amend them, classifying this as Write rather than Destructive.
From the tool's definition Tool description states 'Create a git commit' which modifies the Git repository state by recording changes. Git commits are reversible through operations like git revert or git reset, making this a Write operation rather than Destructive.
Attacks that exploit this kind of access
Create a git commit. It is categorised as a Write tool in the Coding MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Coding MCP Server MCP server in PolicyLayer and add a rule for git_commit: 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 Coding MCP Server. Nothing to install.
git_commit 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 git_commit 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 git_commit. 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.
git_commit is provided by the Coding MCP Server MCP server (kieutrongthien/coding-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →