# deploy_service_from_image

Deploy a container image from Artifact Registry or Docker Hub as a Cloud Run service.

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

## Facts

- Tool: `deploy_service_from_image`
- 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_image",
    "arguments": {
      "service": {}
    }
  }
}
```

## Why deploy_service_from_image is rated High

This tool executes arbitrary container code in Google Cloud Run, which is a code execution operation with significant blast radius. While it doesn't permanently delete data (Destructive) or move money (Financial), it runs external operations that could modify infrastructure, consume resources, or compromise systems depending on malicious image contents.

From the tool's own definition: "Tool deploys a container image as a Cloud Run service. The description explicitly states 'Deploy a container image...as a Cloud Run service,' indicating execution of containerized code in a managed environment."

## Use case

AI agents invoke deploy_service_from_image 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_image": {
      "limits": [
        {
          "counter": "deploy_service_from_image_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Google Cloud Run (4)

- `deploy_service_from_archive` — Execute — https://policylayer.com/tools/com-googleapis-run-mcp/deploy-service-from-archive.md
- `deploy_service_from_file_contents` — Execute — https://policylayer.com/tools/com-googleapis-run-mcp/deploy-service-from-file-contents.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