AI agents use git_add to create or update resources in LuzzyTool — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LuzzyTool environment.
git_add stages files for commit without permanently modifying the repository. This is a reversible change operation (files can be unstaged), making it a Write action rather than Destructive or Execute. Severity is medium because staging changes prepares them for potential commit, but the changes remain uncommitted and reversible. The tool does not execute arbitrary code, delete data, or handle financial operations.
From the tool's definition Tool description states '【暂存操作】将文件添加到 Git 暂存区' (staging operation - add files to Git staging area). The tool modifies the Git index/staging area by adding specified files or all changes.
Attacks that exploit this kind of access
【暂存操作】将文件添加到 Git 暂存区。paths 指定文件列表,all=true 暂存所有变更。. It is categorised as a Write tool in the LuzzyTool MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LuzzyTool 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 LuzzyTool. 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 LuzzyTool MCP server (luzzymeow/luzzytool). 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 →