Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/GoogleCloudPlatform/cloud-run-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/plugins/googlecloudplatform/cloud-run-mcp/gemini-extension)<a href="https://agentmods.dev/plugins/googlecloudplatform/cloud-run-mcp/gemini-extension"><img src="https://agentmods.dev/badge/plugins/googlecloudplatform/cloud-run-mcp/gemini-extension/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/plugins/googlecloudplatform/cloud-run-mcp/gemini-extension"><img src="https://agentmods.dev/badge/plugins/googlecloudplatform/cloud-run-mcp/gemini-extension.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
cloud-run scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"name": "cloud-run",
"version": "1.0.0",
"mcpServers": {
"cloud-run": {
"command": "npx",
"args": ["-y", "@google-cloud/cloud-run-mcp"]
}
},
"settings": [
{
"name": "Project ID",
"description": "Google Cloud project ID to use for Cloud Run operations.",
"envVar": "GOOGLE_CLOUD_PROJECT"
},
{
"name": "Region",
"description": "Google Cloud region where Cloud Run services will be managed.",
"envVar": "GOOGLE_CLOUD_REGION"
}
],
"contextFileName": "gemini-extension/GEMINI.md"
}
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 24 lines scan A f3966abaf5bd
cloud-run is a plugin published in the GitHub repository GoogleCloudPlatform/cloud-run-mcp (633 stars, last pushed 7d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-10.
Other plugins, from other repositories
unifi-network
UniFi Network MCP server — manage network devices, clients, firewall, VPN, and more.
harness-mcp
AI-native interface to the Harness Platform — ask questions, diagnose failures, and manage deployments without leaving your terminal.
acronis
The first real CLI for the Acronis Cyber Protect Cloud platform — every tenant, agent, and usage metric mirrored locally, with cross-tenant rollups no single API call returns.
aws-billing
Get a non-expert from zero to a Slack-delivered, plain-English, waste-flagged AWS bill breakdown - and cache it so you don't pay per Cost Explorer call.
axcient
Every x360Recover endpoint, plus the fleet-wide backup-health answers the API alone can't give — offline, joined, and agent-ready.
cove
The first CLI and MCP server for Cove Data Protection — fleet-wide backup health, billing usage, and storage trends from a terminal, with the local history the vendor console doesn't keep.