Execute GCP API calls using TypeScript code
Part of the Gcp MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke run-gcp-code to trigger processes or run actions in Gcp. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
run-gcp-code can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
run-gcp-code:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Gcp policy for all 9 tools.
Execute GCP API calls using TypeScript code. It is categorised as a Execute tool in the Gcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for run-gcp-code. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Gcp MCP server.
run-gcp-code is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run-gcp-code rule in your Intercept 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.
Set action: deny in the Intercept policy for run-gcp-code. 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.
run-gcp-code is provided by the Gcp MCP server (gcp-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept