Create an annotated git tag
AI agents use git_create_tag to create or update resources in Coding MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Coding MCP Server environment.
Creating a git tag is a reversible write operation that modifies the repository state by adding metadata (the tag), but does not alter source code or delete data. While tags can be deleted, the primary action is creation/modification. The severity is medium because misuse could pollute version history or mislead deployments, but the impact is recoverable through tag deletion.
From the tool's definition Tool name 'git_create_tag' and description 'Create an annotated git tag' indicate a write operation that creates a new git tag object.
Attacks that exploit this kind of access
Create an annotated git tag. It is categorised as a Write tool in the Coding MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Coding MCP Server MCP server in PolicyLayer and add a rule for git_create_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 Coding MCP Server. Nothing to install.
git_create_tag is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the git_create_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 git_create_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.
git_create_tag is provided by the Coding MCP Server MCP server (kieutrongthien/coding-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →