Restore files from git index or HEAD
AI agents call git_restore to permanently remove resources in Coding MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
git restore overwrites working tree files with content from the index or HEAD, discarding any uncommitted local changes. This operation is irreversible — local modifications that haven't been staged or committed are permanently lost. This makes it Destructive, with high severity since an AI agent could inadvertently wipe unsaved work across files or entire directories.
From the tool's definition Restore files from git index or HEAD
Attacks that exploit this kind of access
Restore files from git index or HEAD. It is categorised as a Destructive tool in the Coding MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Coding MCP Server MCP server in PolicyLayer and add a rule for git_restore: 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_restore is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the git_restore 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_restore. 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_restore 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 →