cloud-run-mcp@1.12.0

CAUTION

Publisher claims: "MCP server to deploy apps to Cloud Run" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry Docker MCP CatalogPublisher googlecloudplatform · joined 12 days agoInstalls 45,174Last detonated 2 h ago

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-11-06 and scored it 78/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 60 s · 2 scenarios
t+CategoryObserved action
0.0sprocessno install scripts in bundle
60sprocessdependency install exceeded 60s
60sprocessexec /usr/bin/date
60sprocessexec /usr/bin/timeout
60sclaimedno tools/list reply (exit 0)
60sprocessscript backend runs setup only
60sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathsmcp-server.js:41 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
File type combined with upload actiontest/need-gcp/test-helpers.js:178 · File type combined with upload action — agent may exfiltrate local data filesFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.
AST07
MEDIUM
File type combined with upload actiontest/need-gcp/test-helpers.js:171 · File type combined with upload action — agent may exfiltrate local data filesFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.
AST07
MEDIUM
Destructive file system command detectedexample-sources-to-deploy/golang/Dockerfile:43 · Destructive file system command detectedFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05

Cost to the agent

Instructions loaded
≈1,294 tok
2 files · 80 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.

What would make this Verified

2 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim googlecloudplatform: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. Does not do what the description says≈ +5 on the totalIn the sandbox the skill never performed the task it claims (no call to the service it is for). Make sure the happy path runs without extra setup, or describe the real behavior.
  3. Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
  4. New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
  5. File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.
  6. Destructive file system command detected≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
Publish a new version to Docker MCP Catalog, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim googlecloudplatformPropose a patch to the maintainer