Google Cloud Run MCP server
5 tools · Last check that passed 27 Oct 2026, 01:50 UTC
Google's own remote MCP server for Cloud Run gives an agent the Cloud Run services of the Google Cloud projects its sign-in reaches, and can deploy new ones. Once a day, Stackduke connects to it the way any MCP client would, with no account and no sign-in, and lists its tools. It never runs them.
All 5 tools
| Tool | Counted as |
|---|---|
deploy_service_from_archive | Deletes |
deploy_service_from_file_contents | Deletes |
deploy_service_from_image | Deletes |
get_service | Said to only read |
list_services | Said to only read |
The tools the server listed at the last check that passed, at its default address and settings, with no sign-in; an account that signs in, or other settings, may see other tools. What a tool is counted as doing is Stackduke's cautious reading of the server's labels, the tool's name and its description: where they disagree it takes whichever says the tool can do most, so it overcounts on purpose. It does not say the server is safe, and it does not list what a tool cannot do. Descriptions are not shown, because they are written for models and may try to steer them.
Recent checks
12 of the last 12 checks passed
A check passes when the server lists its tools. Checked at https://run.googleapis.com/mcp.
Recent changes
No change seen across the last 12 checks that passed.
From the scan of 27 Oct 2026, 01:52 UTC. "Changed" and "Can do more" count changes from the last 30 days; older ones stay listed here. A change made and undone between two checks is not seen. Every check is in the scanner's public data.
Know when Google Cloud Run's tools change.
One email when Google Cloud Run's official MCP server adds, removes or changes tools, with what changed. Nothing else.
What to watch for
- An agent can deploy a public or private web service from a container image, from source files or from a zip file, to the project and region it names. Google's Cloud Run MCP documentation
- Its run scope allows access to read and modify data. Google's Cloud Run MCP documentation
How to limit it
With Google Cloud Run's own settings, as its documentation describes them. Stackduke has not tested them.
- Sign in with the run.readonly scope when the agent only needs to read. Google says it only allows access to read data. Google's Cloud Run MCP documentation
- Google recommends a separate identity for agents that use MCP tools, so that their access can be controlled and monitored. Google's Cloud Run MCP documentation
- IAM allow and deny policies can allow or refuse tool calls by principal, by service or tool name, by the application's OAuth client, or by whether a tool is marked read-only. Google's Cloud Run MCP documentation
What Stackduke is designed to do
Stackduke is designed to sit between your agents and their MCP servers: to check each tool call against your rules before it runs, hold the risky ones for a person to approve, and keep a record of what was decided.
It does not yet forward or block tool calls for customers. Today it reads what this server offers and publishes what changes.