get_service
Get info about a Cloud Run service, such as its URI and whether the deploy succeeded.
This record as markdown: /tools/com-googleapis-run-mcp/get-service.md
What get_service does on Google Cloud Run
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.
| 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.
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 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'.
Attacks that exploit this kind of access
The rule that runs get_service 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 get_service, this is the rule to start with:
get_service 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 get_service call is checked against it from then on.
Questions about get_service
Get info about a Cloud Run service, such as its URI and whether the deploy succeeded. It is categorised as a Read tool in the Google Cloud Run MCP Server, which means it retrieves data without modifying state.
get_service accepts 3 parameters: name, region, project. Required: name, 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 get_service: 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.
get_service 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 get_service 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 get_service. 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.
get_service 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