Resets the current HEAD to a specified state. Supports soft, mixed, hard, merge, and keep modes. The
AI agents call reset to permanently remove resources in Test — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs irreversible modifications to repository state. Hard reset mode specifically discards working directory changes and can rewrite history. Even soft/mixed modes can discard staged changes. The capability to reset HEAD to arbitrary states makes this a destructive operation that cannot be reliably recovered from in all scenarios, placing it above Execute category.
From the tool's definition Tool name 'reset' with description 'Resets the current HEAD to a specified state' indicates git reset functionality. Git reset in hard, merge, or keep modes irreversibly discards uncommitted changes and can rewrite commit history.
Documented attack patterns abuse exactly the kind of access reset gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Test, and nothing reaches the server without passing your rules. This is the rule we recommend for reset:
{
"version": "1",
"default": "deny",
"hide": [
"reset"
]
} reset disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Resets the current HEAD to a specified state. Supports soft, mixed, hard, merge, and keep modes. The. It is categorised as a Destructive tool in the Test MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Test MCP server in PolicyLayer and add a rule for reset: 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 Test. Nothing to install.
reset 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 reset 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 reset. 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.
reset is provided by the Test MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Test, 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.
202 Test tools catalogued and risk-classified — across an index of 43,000+ MCP servers.