This record as markdown: /tools/io-github-dave-london-git/tag.md
What tag does on Git
AI agents call tag to permanently remove resources in Git, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why tag is rated Critical
While the tool primarily supports read (list) and write (create) operations, the delete action is irreversible and can remove git tags that may be important for version control, release management, or project history. This destructive capability makes it the most severe applicable category. An AI agent with access to this tool could permanently remove critical tags from a repository.
From the tool's definition Tool description explicitly states it 'Supports list (default), create, and delete actions' with delete capability for git tags.
Attacks that exploit this kind of access
The rule that runs tag safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Git, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tag, this is the rule to start with:
tag is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Git, apply this rule, and every tag call is checked against it from then on.
Questions about 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. 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.
Register the Git MCP server in PolicyLayer and add a rule for 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 Git. Nothing to install.
tag 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 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.
Set action: deny in the PolicyLayer 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.
tag is provided by the Git MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Git, and thousands of servers like it.
Across the catalogue