deploy_service_from_file_contents

SERVERGoogle Cloud Run SOURCEhttps://run.googleapis.com/mcp

High RISK CLASS

Category Execute

Parameters 11 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-googleapis-run-mcp/deploy-service-from-file-contents.md

WHAT IT DOES

What deploy_service_from_file_contents does on Google Cloud Run

AI agents invoke deploy_service_from_file_contents to trigger actions in Google Cloud Run. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`service`	object	Yes	Required. The service to deploy.

Parameters from the server's own tool schema.

RISK

Why deploy_service_from_file_contents is rated High

deploy_service_from_file_contents triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs deploy_service_from_file_contents safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Google Cloud Run, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For deploy_service_from_file_contents, this is the rule to start with:

deploy_service_from_file_contents Rate-limited

deploy_service_from_file_contents stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "deploy_service_from_file_contents": {
      "limits": [
        {
          "counter": "deploy_service_from_file_contents_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Google Cloud Run, apply this rule, and every deploy_service_from_file_contents call is checked against it from then on.

FAQ

Questions about deploy_service_from_file_contents

What does the deploy_service_from_file_contents tool do? +

Deploys a Cloud Run service directly from local source files. This method is suitable for scripting languages like Python and Node.js, of which the source code can be embedded in the request. This is ideal for quick tests and development feedback loops. You must include all necessary dependencies within the source files because it skips the build step for faster deployment. Key Requirements: 1. source_code: Should set to sourceCode.inlinedSource.sources with array of source files, each having filename and content. 2. Size limit: you are subject to total request size limit of 50MiB. It is categorised as a Execute tool in the Google Cloud Run MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does deploy_service_from_file_contents accept? +

deploy_service_from_file_contents accepts 1 parameter: service. Required: service. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on deploy_service_from_file_contents? +

Register the Google Cloud Run MCP server in PolicyLayer and add a rule for deploy_service_from_file_contents: 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 deploy_service_from_file_contents? +

deploy_service_from_file_contents is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit deploy_service_from_file_contents? +

Yes. Add a rate_limit block to the deploy_service_from_file_contents 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 deploy_service_from_file_contents completely? +

Set action: deny in the PolicyLayer policy for deploy_service_from_file_contents. 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 deploy_service_from_file_contents? +

deploy_service_from_file_contents 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.

KEEP EXPLORING

More on Google Cloud Run, and thousands of servers like it.

This server

All 5 Google Cloud Run tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →