Critical Risk →

tag

Manages git tags. Supports list (default), create, and delete actions. List returns structured tag data with name, date, and message. Create supports lightweight and annotated tags.

Accepts file system path (path); High parameter count (15 properties)

Part of the Git MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@paretools/git Destructive Risk 5/5

AI agents may call tag to permanently remove or destroy resources in Git. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call tag in a loop, permanently destroying resources in Git. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

io-github-dave-london-git.yaml
tools:
  tag:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Git policy for all 28 tools.

Tool Name tag
Category Destructive
MCP Server Git MCP Server
Risk Level Critical

View all 28 tools →

Agents calling destructive-class tools like tag have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

tag is one of the critical-risk operations in Git. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the tag tool do? +

Manages git tags. Supports list (default), create, and delete actions. List returns structured tag data with name, date, and message. Create supports lightweight and annotated tags.. It is categorised as a Destructive tool in the Git 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 tag? +

Add a rule in your Intercept YAML policy under the tools section for tag. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Git MCP server.

What risk level is tag? +

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 tag? +

Yes. Add a rate_limit block to the tag rule in your Intercept 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 tag completely? +

Set action: deny in the Intercept policy for 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 tag? +

tag is provided by the Git MCP server (@paretools/git). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Git

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.