get_tag

get_tag

Server Kepler MCP GitLab Server ryan-rbw/kepler-mcp-gitlab-server
Category Read
Risk class Low
Parameters 00 required

What get_tag does on Kepler MCP GitLab Server

AI agents call get_tag to retrieve information from Kepler MCP GitLab Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_tag needs a policy

The name 'get_tag' strongly indicates a retrieval operation. In GitLab workflows, 'get' operations typically fetch information about objects (tags, commits, branches) without side effects. Although the description is empty (lowering confidence slightly), the naming pattern and server context support classification as a Read operation with low severity.

From the tool's definition Tool name 'get_tag' combined with context of a GitLab integration server suggests retrieval of tag metadata or information. No creation, modification, deletion, or execution indicators present.

Questions about get_tag

What does the get_tag tool do? +

get_tag. It is categorised as a Read tool in the Kepler MCP GitLab Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_tag? +

Register the Kepler MCP GitLab Server 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 Kepler MCP GitLab Server. Nothing to install.

What risk level is get_tag? +

get_tag is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_tag? +

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.

How do I block get_tag completely? +

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.

What MCP server provides get_tag? +

get_tag is provided by the Kepler MCP GitLab Server MCP server (ryan-rbw/kepler-mcp-gitlab-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.