git_reset

A destructive tool on the GitHub MCP server.

SERVERGitHub SOURCEoci:ghcr.io/aifity/omnigit-mcp:0.5.0

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-aifity-omnigit-mcp/git-reset.md

WHAT IT DOES

What git_reset does on GitHub

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

RISK

Why git_reset is rated Critical

git reset --hard is irreversible and can permanently destroy uncommitted changes and move branch pointers, potentially losing work across a repository. Even softer modes can have significant unintended consequences when misused by an AI agent. The most severe applicable category is Destructive given the potential for irreversible data loss.

From the tool's definition Tool name: 'git_reset' — a git reset operation can rewrite commit history, discard staged changes, or remove commits depending on mode (--soft, --mixed, --hard). A hard reset irreversibly discards working tree changes and commits.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs git_reset safely

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

git_reset Hidden

git_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": [
    "git_reset"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about git_reset

What does the git_reset tool do? +

git_reset is a destructive tool on the GitHub MCP server. It is categorised as a Destructive tool in the GitHub 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 git_reset? +

Register the GitHub MCP server in PolicyLayer and add a rule for git_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 GitHub. Nothing to install.

What risk level is git_reset? +

git_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 git_reset? +

Yes. Add a rate_limit block to the git_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 git_reset completely? +

Set action: deny in the PolicyLayer policy for git_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 git_reset? +

git_reset is provided by the GitHub MCP server (oci:ghcr.io/aifity/omnigit-mcp:0.5.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GitHub, and thousands of servers like it.

This server

All 245 GitHub tools → Critical-risk tools on this server →

Across the catalogue

team_manager_reset on Team Manager MCP →delete_git_repo on cPanel MCP Server →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 →