AI agents use git_add to create or update resources in MCP File Edit — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP File Edit environment.
git_add modifies the git index/staging area but does not delete data, execute arbitrary code, or cause irreversible changes. The operation is reversible (files can be unstaged via git reset). This is a Write-category tool because it creates or modifies repository state.
From the tool's definition Tool performs 'Add files to git staging area' — a reversible modification operation that stages changes for commit without destructive effects.
Documented attack patterns abuse exactly the kind of access git_add gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP File Edit, and nothing reaches the server without passing your rules. This is the rule we recommend for git_add:
{
"version": "1",
"default": "deny",
"tools": {
"git_add": {
"limits": [
{
"counter": "git_add_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}git_add 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.
Free to start. No card required.
Add files to git staging area. It is categorised as a Write tool in the MCP File Edit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP File Edit 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 MCP File Edit. 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 MCP File Edit MCP server (patrickomatik/mcp-file-edit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP File Edit, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
32 MCP File Edit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.