reset

Resets the current HEAD to a specified state. Supports soft, mixed, hard, merge, and keep modes. The

SERVERDocker SOURCE@paretools/docker

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dave-london-docker/reset.md

WHAT IT DOES

What reset does on Docker

AI agents call reset to permanently remove resources in Docker, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why reset is rated Critical

The reset tool, particularly in 'hard' mode, irreversibly modifies or discards repository state and cannot be undone without access to reflog. This fits Destructive (irreversible data loss/modification) rather than Execute (reversible side effects). High severity due to potential loss of uncommitted work and commit history rewriting.

From the tool's definition 'Resets the current HEAD to a specified state' with support for 'hard' mode, which irreversibly discards uncommitted changes and rewrites commit history.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs reset safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Docker, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reset, this is the rule to start with:

reset Hidden

reset is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "reset"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Docker, apply this rule, and every reset call is checked against it from then on.

FAQ

Questions about reset

What does the reset tool do? +

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 Docker MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on reset? +

Register the Docker 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 Docker. Nothing to install.

What risk level is reset? +

reset is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit reset? +

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.

How do I block reset completely? +

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.

What MCP server provides reset? +

reset is provided by the Docker MCP server (@paretools/docker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Docker, and thousands of servers like it.

This server

All 202 Docker tools → Critical-risk tools on this server →

Across the catalogue

team_manager_reset on Team Manager MCP →reset_mcp_runtime_metrics on 0xpdf → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →