list_services
List Cloud Run services in a given Google Cloud project and region.
This record as markdown: /tools/com-googleapis-run-mcp/list-services.md
What list_services does on Google Cloud Run
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.
| 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.
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 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…
Attacks that exploit this kind of access
The rule that runs list_services safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Google Cloud Run, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_services, this is the rule to start with:
list_services is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Google Cloud Run, apply this rule, and every list_services call is checked against it from then on.
Questions about list_services
List Cloud Run services in a given Google Cloud project and region. It is categorised as a Read tool in the Google Cloud Run MCP Server, which means it retrieves data without modifying state.
list_services accepts 2 parameters: region, project. Required: region, project. The full parameter table on this page comes from the server's own tool schema.
Register the Google Cloud Run MCP server in PolicyLayer and add a rule for list_services: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Google Cloud Run. Nothing to install.
list_services is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_services rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for list_services. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
list_services is provided by the Google Cloud Run MCP server (https://run.googleapis.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Google Cloud Run, and thousands of servers like it.
This server
Across the catalogue