# 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 deployment. The archive must include all dependencies: - For compiled languages (Go, Java), include pre-compiled binaries. - For scripting languages (Python, Node.js), include pre-installed libraries (e.g., vendor/, node_modules/). Deployment steps: 1. Package source code and dependencies into a .tar.gz archive (max 250MiB). It's recommended to create archive from the root of the application's source directory. 2. Upload the archive to a Google Cloud Storage bucket, preferably in the same region as the service. 3. Deploy to Cloud Run using this tool, specifying: - source_code: Google Cloud Storage object path to the archive (e.g., gs://bucket/object). - command: Command to start the application. - base_image_uri: Base image for the container (e.g., go124, nodejs24, python314). See https://docs.cloud.google.com/run/docs/configuring/services/runtime-base-images for options. The runtime picked should match the local environment. - args: (Optional) Arguments for the command. - env: (Optional) Environment variables (e.g., name: PYTHONPATH, value: ./vendor). - ports: (Optional) Container ports to expose (defaults to 8080).

Agent View of the PolicyLayer registry record for `deploy_service_from_archive`. HTML page: https://policylayer.com/tools/com-googleapis-run-mcp/deploy-service-from-archive

## Facts

- Tool: `deploy_service_from_archive`
- Server: Google Cloud Run (`https://run.googleapis.com/mcp`) — https://policylayer.com/tools/com-googleapis-run-mcp.md
- Homepage: https://github.com/https://run.googleapis.com/mcp
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `service` | object | yes | Required. The service to deploy. |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "deploy_service_from_archive",
    "arguments": {
      "service": {}
    }
  }
}
```

## Why deploy_service_from_archive is rated High

deploy_service_from_archive triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Risk signals: Admin/system-level operation

## Use case

AI agents invoke deploy_service_from_archive to trigger actions in Google Cloud Run. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Google Cloud Run:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "deploy_service_from_archive": {
      "limits": [
        {
          "counter": "deploy_service_from_archive_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Google Cloud Run (4)

- `deploy_service_from_file_contents` — Execute — https://policylayer.com/tools/com-googleapis-run-mcp/deploy-service-from-file-contents.md
- `deploy_service_from_image` — Execute — https://policylayer.com/tools/com-googleapis-run-mcp/deploy-service-from-image.md
- `get_service` — Read — https://policylayer.com/tools/com-googleapis-run-mcp/get-service.md
- `list_services` — Read — https://policylayer.com/tools/com-googleapis-run-mcp/list-services.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-googleapis-run-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-googleapis-run-mcp