Removes files from version control
AI agents call hg_remove to permanently remove resources in Mercurial — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
File removal from version control is a destructive operation that cannot be easily undone without access to repository history. While the actual file may still exist on disk (depending on flags), the removal from version control is a state change that modifies the repository in a way that affects all future operations.
From the tool's definition Tool name 'hg_remove' and description 'Removes files from version control' indicate irreversible deletion of tracked files from the repository. This mirrors git rm behavior, which permanently removes files from version control.
Attacks that exploit this kind of access
Removes files from version control. It is categorised as a Destructive tool in the Mercurial MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mercurial MCP server in PolicyLayer and add a rule for hg_remove: 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 Mercurial. Nothing to install.
hg_remove 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 hg_remove 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 hg_remove. 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.
hg_remove is provided by the Mercurial MCP server (metal-shark-sharktech/mcp-server-mercurial). 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 →