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.

How to control tag ↓

What tag does on Python

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

Critical Risk

Why tag needs a policy

While the tool also supports read (list) and write (create) operations, the presence of a delete action for git tags qualifies it as Destructive. Deleting git tags is an irreversible operation that can break builds, releases, and version control history, making it the most severe category applicable. The delete capability places this tool in the Destructive category per the severity hierarchy.

From the tool's definition Tool description explicitly states it 'Supports list (default), create, and delete actions' with delete capability for git tags. The delete action is irreversible once pushed to remote repositories.

Documented attack patterns abuse exactly the kind of access tag gives an agent:

How to control tag

PolicyLayer is an MCP gateway — it sits between your AI agents and Python, and nothing reaches the server without passing your rules. This is the rule we recommend for tag:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "tag"
  ]
}

tag disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Python — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about tag

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

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

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

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.

What MCP server provides tag? +

tag is provided by the Python MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Python tool call.

Start from Python, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

202 Python tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.