List all tags in the repository. Displays all tag names that exist in the repository, which can be used to identify releases or important reference points.
AI agents call git_tag_list to retrieve information from Git MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
git_tag_list queries and returns existing tag data without modifying, deleting, or executing any operations. It is purely informational, analogous to 'git tag' in list mode. The blast radius of misuse is minimal; an agent could only enumerate tags, not alter repository state.
From the tool's definition Tool description states 'List all tags in the repository. Displays all tag names' — a read-only retrieval operation with no side effects.
Attacks that exploit this kind of access
List all tags in the repository. Displays all tag names that exist in the repository, which can be used to identify releases or important reference points. It is categorised as a Read tool in the Git MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Git MCP Server MCP server in PolicyLayer and add a rule for git_tag_list: 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 MCP Server. Nothing to install.
git_tag_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the git_tag_list 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_tag_list. 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_tag_list is provided by the Git MCP Server MCP server (wty0512/git-mcp-server). 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 →