gcp_ar_delete_repository
Delete an Artifact Registry repository
This record as markdown: /tools/ahmedselimmansor-ctrl-gcp-mcp-server/gcp-ar-delete-repository.md
What gcp_ar_delete_repository does on GCP MCP Server
AI agents call gcp_ar_delete_repository to permanently remove resources in GCP MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why gcp_ar_delete_repository is rated Critical
Deleting an Artifact Registry repository is an irreversible action that destroys data and cannot be undone. This is the defining characteristic of the Destructive category. The blast radius is high because a misused tool could destroy critical container images, dependencies, or build artifacts that applications depend on, potentially breaking deployments and services.
From the tool's definition Tool name is 'gcp_ar_delete_repository' and description states 'Delete an Artifact Registry repository'. The verb 'Delete' combined with the irreversible nature of removing a repository containing artifacts, images, or packages makes this a destructive…
Attacks that exploit this kind of access
The rule that runs gcp_ar_delete_repository safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GCP MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gcp_ar_delete_repository, this is the rule to start with:
gcp_ar_delete_repository 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 GCP MCP Server, apply this rule, and every gcp_ar_delete_repository call is checked against it from then on.
Questions about gcp_ar_delete_repository
Delete an Artifact Registry repository. It is categorised as a Destructive tool in the GCP MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the GCP MCP Server MCP server in PolicyLayer and add a rule for gcp_ar_delete_repository: 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 GCP MCP Server. Nothing to install.
gcp_ar_delete_repository 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 gcp_ar_delete_repository 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 gcp_ar_delete_repository. 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.
gcp_ar_delete_repository is provided by the GCP MCP Server MCP server (ahmedselimmansor-ctrl/gcp_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GCP MCP Server, and thousands of servers like it.
Across the catalogue