New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_service

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

SERVERGoogle Cloud Run SOURCEhttps://run.googleapis.com/mcp
Low RISK CLASS
Category Read
Parameters 33 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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'.

Questions about get_service

What does the get_service tool do? +

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.

What parameters does get_service accept? +

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.

How do I enforce a policy on get_service? +

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.

What risk level is get_service? +

get_service is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_service? +

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.

How do I block get_service completely? +

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.

What MCP server provides get_service? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Google Cloud Run's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.