execute_stack_command · Terragrunt GCP Tool MCP

WHAT IT DOES

What execute_stack_command does on Terragrunt GCP Tool MCP

AI agents invoke execute_stack_command 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 execute_stack_command needs a policy

This tool allows execution of commands against GCP infrastructure stacks with parallel processing. While the description does not specify destructive operations, the ability to execute arbitrary stack commands creates significant risk of unintended infrastructure changes, service disruptions, or resource modifications.

From the tool's definition execute_stack_command - Execute commands on stacks with parallel execution and dependency management. The verb 'Execute' combined with 'commands on stacks' and reference to 'parallel execution' indicates this tool runs arbitrary operations against…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_stack_command Rate-limited

execute_stack_command 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": {
    "execute_stack_command": {
      "limits": [
        {
          "counter": "execute_stack_command_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 execute_stack_command

What does the execute_stack_command tool do? +

Execute commands on stacks with parallel execution and dependency management. 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 execute_stack_command? +

Register the Terragrunt GCP Tool MCP server in PolicyLayer and add a rule for execute_stack_command: 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 execute_stack_command? +

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

Can I rate-limit execute_stack_command? +

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

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

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