// SCAN REPORT

Google Cloud Run

5 tools. 3 can modify or destroy data without limits.

3 write tools that can modify data. Rate limits recommended.

Last updated: 3 Sept 2026

3 can modify or destroy data

2 read-only

5 tools total

Community server · catalogue entry checked 03/09/2026 · full schemas captured for 5 of 5 tools

How to control Google Cloud Run ↓

TOOL MAP

What Google Cloud Run exposes to your agents

Read (2) Write / Execute (3) Destructive / Financial (0)

Running more than one server? Check your whole stack →

CONTEXT-WINDOW COST

What Google Cloud Run costs in tokens

4,752 tokens of tool definitions, loaded on every request

2.4% of a 200k context window

1,836 heaviest tool: deploy_service_from_archive

Full per-tool breakdown → Model it in the token calculator →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Google Cloud Run tools

Execute · High deploy_service_from_image This tool executes arbitrary container code in Google Cloud Run, which is a code execution operation with significant blast radius. Execute · High deploy_service_from_archive Deploy a Cloud Run service directly from a self-contained source code archive (.tar.gz), skipping the container image build step for faster Execute · Medium deploy_service_from_file_contents Deploys a Cloud Run service directly from local source files. This method is suitable for scripting languages like Python and Node.js, of wh

3 of Google Cloud Run's 5 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Google Cloud Run

PolicyLayer is an MCP gateway — it sits between your AI agents and Google Cloud Run, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "get_service": {
    "limits": [
      {
        "counter": "get_service_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Google Cloud Run — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON GOOGLE CLOUD RUN →

Instant setup, no code required.

FULL CATALOGUE

All 5 Google Cloud Run tools

EXECUTE 3 tools

Execute deploy_service_from_archive Deploy a Cloud Run service directly from a self-contained source code archive (.tar.gz), skipping the containe Execute deploy_service_from_file_contents Deploys a Cloud Run service directly from local source files. This method is suitable for scripting languages Execute deploy_service_from_image Deploy a container image from Artifact Registry or Docker Hub as a Cloud Run service.

READ 2 tools

Read get_service Get info about a Cloud Run service, such as its URI and whether the deploy succeeded. Read list_services List Cloud Run services in a given Google Cloud project and region.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Google Cloud Run

Is the Google Cloud Run MCP server safe to use without restrictions? +

The Google Cloud Run server is primarily read-only with 2 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Google Cloud Run MCP server expose? +

5 tools across 2 categories: Execute, Read. 2 are read-only. 3 can modify, create, or delete data.

How do I enforce a policy on Google Cloud Run? +

Register the Google Cloud Run MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Google Cloud Run tool call.

Deterministic rules across all 5 Google Cloud Run tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON GOOGLE CLOUD RUN →

Instant setup, no code required.

5 Google Cloud Run tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Google Cloud Run's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →