purge_dependency_proxy_cache
Schedule purge of all cached dependency proxy blobs for a group
This record as markdown: /tools/io-github-zereight-gitlab-mcp/purge-dependency-proxy-cache.md
What purge_dependency_proxy_cache does on Gitlab Mcp
AI agents call purge_dependency_proxy_cache to permanently remove resources in Gitlab Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why purge_dependency_proxy_cache is rated Critical
This tool deletes cached dependency proxy data at scale (all blobs for a group). While the cache can theoretically be repopulated by re-fetching dependencies, the action itself is irreversible and could disrupt build/deployment pipelines that rely on those cached artifacts.
From the tool's definition Tool name contains 'purge' and description states 'Schedule purge of all cached dependency proxy blobs for a group' — purge indicates irreversible deletion of cached artifacts.
Attacks that exploit this kind of access
The rule that runs purge_dependency_proxy_cache 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 purge_dependency_proxy_cache, this is the rule to start with:
purge_dependency_proxy_cache is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Gitlab Mcp, apply this rule, and every purge_dependency_proxy_cache call is checked against it from then on.
Questions about purge_dependency_proxy_cache
Schedule purge of all cached dependency proxy blobs for a group. It is categorised as a Destructive tool in the Gitlab Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Gitlab MCP server in PolicyLayer and add a rule for purge_dependency_proxy_cache: 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.
purge_dependency_proxy_cache 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 purge_dependency_proxy_cache 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 purge_dependency_proxy_cache. 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.
purge_dependency_proxy_cache 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.
Across the catalogue