Manage GitLab releases: list, view, create, delete.
AI agents call glab_releases to permanently remove resources in RedisNexus — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
While the tool includes read operations (list, view) and write operations (create), the presence of 'delete' functionality for releases—which removes release artifacts, tags, and associated metadata irreversibly—places this tool in the Destructive category. Deleting a release in production environments can break deployments, remove critical version artifacts, and cause significant operational impact.
From the tool's definition Tool description states it can 'list, view, create, delete' GitLab releases. The 'delete' capability is irreversible and destructive.
Attacks that exploit this kind of access
Manage GitLab releases: list, view, create, delete. It is categorised as a Destructive tool in the RedisNexus MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the RedisNexus MCP server in PolicyLayer and add a rule for glab_releases: 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 RedisNexus. Nothing to install.
glab_releases is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the glab_releases 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 glab_releases. 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.
glab_releases is provided by the RedisNexus MCP server (rajkumar-madhu/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 →