Restore a changed file with git restore -- <file>.
AI agents use mcp_git_restore_file to create or update resources in Local Code — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Local Code environment.
The tool reverts file changes, which is a Write operation (modifies data reversibly). It's not Destructive because git restore can be undone by re-applying changes or restoring again from another state. Severity is medium because while it can discard work, it operates within version-controlled scope with undo capability and limited blast radius compared to destructive operations.
From the tool's definition Tool description states 'Restore a changed file with git restore -- <file>', which reverts file modifications to a previous git state. This is a reversible write operation that modifies file contents.
Attacks that exploit this kind of access
Restore a changed file with git restore -- <file>. It is categorised as a Write tool in the Local Code MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Local Code MCP server in PolicyLayer and add a rule for mcp_git_restore_file: 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 Local Code. Nothing to install.
mcp_git_restore_file 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 mcp_git_restore_file 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 mcp_git_restore_file. 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.
mcp_git_restore_file is provided by the Local Code MCP server (js190-prog/local-code-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 →