Stage files with git add
AI agents use git_add 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 add stages files for commit, which is a reversible modification of Git state. While it does not directly alter file contents or delete data, staging changes prepares them for permanent commit. The reversibility (git reset can unstage) and the production context with audit logging place this in Write rather than Execute.
From the tool's definition Tool name 'git_add' and description 'Stage files with git add' indicate it modifies Git's staging area by adding files to be committed.
Attacks that exploit this kind of access
Stage files with git add. 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_add: 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_add 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_add 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_add. 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_add 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 →