This record as markdown: /tools/io-github-zereight-gitlab-mcp/get-tag.md
What get_tag does on Gitlab Mcp
AI agents call get_tag to retrieve information from Gitlab Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_tag is rated Low
This tool retrieves existing tag information from a GitLab repository. It does not modify, delete, or execute any operations—it simply queries and returns data about a specific tag. This is a standard read operation with minimal risk; misuse would only expose existing repository metadata that is typically accessible to authorized users.
From the tool's definition Tool name 'get_tag' combined with description 'Get a repository tag by name' indicates a retrieval operation. The verb 'get' and the read-only nature of fetching tag metadata confirm this is a query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_tag safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gitlab Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_tag, this is the rule to start with:
get_tag is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gitlab Mcp, apply this rule, and every get_tag call is checked against it from then on.
Questions about get_tag
Get a repository tag by name. It is categorised as a Read tool in the Gitlab Mcp MCP Server, which means it retrieves data without modifying state.
Register the Gitlab MCP server in PolicyLayer and add a rule for get_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 Gitlab Mcp. Nothing to install.
get_tag 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 get_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 get_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.
get_tag is provided by the Gitlab MCP server (@zereight/mcp-gitlab). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gitlab, and thousands of servers like it.
This server
Across the catalogue