# get_service

Get info about a Cloud Run service, such as its URI and whether the deploy succeeded.

Agent View of the PolicyLayer registry record for `get_service`. HTML page: https://policylayer.com/tools/com-googleapis-run-mcp/get-service

## Facts

- Tool: `get_service`
- 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: Read (Low risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 3 (3 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `name` | string | yes | Required. The short name of the Service. |
| `region` | string | yes | Required. The region to get the Service from. |
| `project` | string | yes | Required. The project ID or project number to get the Service from. |

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": "get_service",
    "arguments": {
      "name": "<name>",
      "region": "<region>",
      "project": "<project>"
    }
  }
}
```

## Why get_service is rated Low

This tool retrieves information about existing Cloud Run services without modifying, deleting, or executing operations. It is a straightforward read operation that queries service metadata. The worst-case misuse—enumerating service information—has minimal blast radius in a well-segmented environment. Confidence is high given the explicit 'Get' operation and informational focus.

From the tool's own definition: "Tool name and description indicate 'Get info about a Cloud Run service' with retrieval of non-sensitive metadata like 'URI and whether the deploy succeeded'."

## Use case

AI agents call get_service to retrieve information from Google Cloud Run without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_service": {}
  }
}
```

## 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
- `deploy_service_from_image` — Execute — https://policylayer.com/tools/com-googleapis-run-mcp/deploy-service-from-image.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