deploy_resources · Terragrunt GCP Tool MCP: Risk & Policy

WHAT IT DOES

What deploy_resources does on Terragrunt GCP Tool MCP

AI agents invoke deploy_resources to trigger actions in Terragrunt GCP Tool MCP. 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.

WHY IT NEEDS A POLICY

Why deploy_resources needs a policy

This tool triggers deployment operations on Google Cloud Platform infrastructure. While not immediately destructive (the sibling tool delete_resource is explicitly destructive), deploy_resources executes code/commands that provision, modify, or reconfigure cloud resources with real-world effects.

From the tool's definition Tool performs infrastructure deployment via Terragrunt/GCP, which executes external operations that modify cloud resources.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

deploy_resources Rate-limited

deploy_resources 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_resources": {
      "limits": [
        {
          "counter": "deploy_resources_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Terragrunt GCP Tool MCP, so you can run agents against it safely.

FAQ

Questions about deploy_resources

What does the deploy_resources tool do? +

Deploy infrastructure changes (deprecated, use apply_resource_deployment). It is categorised as a Execute tool in the Terragrunt GCP Tool MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on deploy_resources? +

Register the Terragrunt GCP Tool MCP server in PolicyLayer and add a rule for deploy_resources: 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 Terragrunt GCP Tool MCP. Nothing to install.

What risk level is deploy_resources? +

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

Can I rate-limit deploy_resources? +

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

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

deploy_resources is provided by the Terragrunt GCP Tool MCP server (spolspol/terragrunt-gcp-tool-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.