# list_services

List Cloud Run services in a given Google Cloud project and region.

Agent View of the PolicyLayer registry record for `list_services`. HTML page: https://policylayer.com/tools/com-googleapis-run-mcp/list-services

## Facts

- Tool: `list_services`
- 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: 2 (2 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `region` | string | yes | Required. The region to list the Services from. |
| `project` | string | yes | Required. The project ID or project number to list the Services 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": "list_services",
    "arguments": {
      "region": "<region>",
      "project": "<project>"
    }
  }
}
```

## Why list_services is rated Low

This tool retrieves information about Cloud Run services (list operation). It has no side effects and merely enumerates existing resources. Even if an AI agent misuses it by listing services it shouldn't have access to, the blast radius is limited to information disclosure of service names and metadata. No data is modified, destroyed, or financial operations are triggered.

From the tool's own definition: "The tool name is 'list_services' and the description states it 'List[s] Cloud Run services in a given Google Cloud project and region.' This is a read-only operation that retrieves and queries existing service metadata without modifying, executing, or…"

## Use case

AI agents call list_services 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": {
    "list_services": {}
  }
}
```

## 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
- `get_service` — Read — https://policylayer.com/tools/com-googleapis-run-mcp/get-service.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