gcp_ar_create_repository
Create a new Artifact Registry repository
This record as markdown: /tools/ahmedselimmansor-ctrl-gcp-mcp-server/gcp-ar-create-repository.md
What gcp_ar_create_repository does on GCP MCP Server
AI agents use gcp_ar_create_repository to create or update resources in GCP MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GCP MCP Server environment.
Why gcp_ar_create_repository is rated Medium
This tool modifies cloud infrastructure by creating a new repository resource, which is a reversible operation (can be deleted). However, the blast radius is high because an adversary could create repositories to store malicious artifacts, poison supply chains, or consume quota/billing resources. This is Write rather than Execute because it directly creates a resource rather than running arbitrary code or commands.
From the tool's definition Tool creates a new Artifact Registry repository. 'Create' is explicitly a write operation that adds a new resource to GCP. Artifact Registry repositories store build artifacts, container images, and packages—creating one establishes persistent infrastructure.
Attacks that exploit this kind of access
The rule that runs gcp_ar_create_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_create_repository, this is the rule to start with:
gcp_ar_create_repository stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GCP MCP Server, apply this rule, and every gcp_ar_create_repository call is checked against it from then on.
Questions about gcp_ar_create_repository
Create a new Artifact Registry repository. It is categorised as a Write tool in the GCP MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GCP MCP Server MCP server in PolicyLayer and add a rule for gcp_ar_create_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_create_repository is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the gcp_ar_create_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_create_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_create_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.
This server
Across the catalogue