How is this different from connecting Google Cloud Run MCP directly?

Connected directly, an agent sees every tool the server exposes and holds the credential itself. Through TrustGate you choose which tools each agent gets, and every call is logged against the agent that made it.

What if the Google Cloud Run MCP API changes?

We track the Google Cloud Run MCP schema, so the tool catalogue stays current. Tools you have already allowed keep working, and anything new stays denied until you enable it.

Can I give different agents different Google Cloud Run tools?

Yes. Access is set per agent: one can get a handful of read tools, another the full set. You grant the whole MCP or single tools within it.

Where can I see what my agents did in Google Cloud Run?

Every call is logged against the agent that made it, with the tool it used. Activity can be sent on to your own monitoring.

Do I need to run the Google Cloud Run MCP server myself?

No. TrustGate connects to the Google Cloud Run MCP server and sits in front of it. Your agent only talks to your TrustGate URL, never to Google Cloud Run directly.

Connect Google Cloud Run MCP to your AI agents, securely.

Q: Is Google Cloud Run MCP secure?

The server itself exposes 5 tools, and some of them can write to your Google Cloud Run account. Behind TrustGate an agent only sees the tools you allow, requests and responses are inspected, and every call is logged. Anything outside the allowlist is denied before it reaches Google Cloud Run.

One secured endpoint for every Google Cloud Run call your AI agents make, scoped per user, inspected, and logged.

Get started for free

Get a demo

Try Google Cloud Run MCP now

What your agents can ask once Google Cloud Run MCP is connected.

Select the tools your AI agents can call

5 tools from the Google Cloud Run MCP schema.

Showing 5 tools

list_servicesreadLists Cloud Run services in a given project and location.
get_servicereadGets the details of a specific Cloud Run service.
deploy_service_from_imagewriteDeploy a container image from Artifact Registry or Docker Hub as a Cloud Run service.
deploy_service_from_archivewriteDeploy a Cloud Run service directly from a self-contained source code archive (.tar.gz), skipping the container image build step for faster deployment.
deploy_service_from_file_contentswriteDeploys a Cloud Run service directly from local source files.

What Google Cloud Run MCP exposes

Google Cloud Run MCP groups its 5 tools into 1 categories, each with a suggested starting policy.

All 5 tools as JSON, ready to paste.

Category	Covers	Access	Suggested policy
Services	Service listing, details, creation, updates and deletion	Read / Write	Approve deployments; require approval for deletes

Connect Google Cloud Run MCP to your AI agent

Four steps, under ten minutes.

01
Sign in to NeuralTrust
Open the NeuralTrust platform, sign in and go to Getting started, then Connect your tools.
02
Choose your agent
When asked which agent you use, pick Claude Code, Codex, Cursor, Windsurf, Copilot or your own code.
03
Connect Google Cloud Run
Find Google Cloud Run in the tool list and connect it.
04
Connect your agent
Follow the steps on screen to add the config to your agent, then send the test prompt.

Permissions down to the single tool

You do not allow Google Cloud Run MCP or block it. You allow the exact tools each agent can call, one by one.

Google Cloud Run MCP	5 TOOLS AVAILABLE
Code review agent	4 tools, read only
Issue triage bot	9 tools
Platform team assistant	all 5 tools

Tool by toolConnecting the server is not the unit of access. Each tool is granted on its own.
Default denyA tool you have not enabled is never exposed to the agent.
Approval on writesTools that change or delete things can require a human to confirm.

Is Google Cloud Run MCP secure?

One endpoint instead of raw credentials. Every call is checked against policy and logged.

AI agentsConnect through your MCP client configuration.	NeuralTrustApply controls based on your configuration.	Google Cloud Run MCP5 documented tools.
Coding assistants	Connection & credentialsper user	Services5 tools
Internal copilots	Tool access policiesdeny by default
Workflow automations	Request & response inspectioninline
Compatible MCP clients	Activity monitoringalerts and logs