git_tag

Manage Git tags: create, list, delete, or show tag details

SERVERGitHub MCP Server SOURCE0xshariq/github-mcp-server

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/0xshariq-github-mcp-server/git-tag.md

WHAT IT DOES

What git_tag does on GitHub MCP Server

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

RISK

Why git_tag is rated Critical

The tool explicitly supports 'delete' operations on Git tags, which is irreversible (especially for pushed tags). Since the tool spans multiple categories (Read for list/show, Write for create, Destructive for delete), the most severe applicable category is Destructive. Deleting tags—particularly remote tags—cannot be undone and can break references in CI/CD pipelines or release workflows.

From the tool's definition Manage Git tags: create, list, delete, or show tag details

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs git_tag safely

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

git_tag Hidden

git_tag 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_tag"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about git_tag

What does the git_tag tool do? +

Manage Git tags: create, list, delete, or show tag details. It is categorised as a Destructive tool in the GitHub MCP Server 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_tag? +

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

What risk level is git_tag? +

git_tag 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_tag? +

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

Set action: deny in the PolicyLayer policy for git_tag. 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_tag? +

git_tag is provided by the GitHub MCP Server MCP server (0xshariq/github-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GitHub MCP Server, and thousands of servers like it.

This server

All 33 GitHub MCP Server tools → Critical-risk tools on this server →

Across the catalogue

delete_git_repo on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

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