gcp-utils-set-project-id

THE RISK

Medium Risk

Why gcp-utils-set-project-id needs a policy

This tool modifies configuration state (the active project context) which is a reversible write operation. While not destructive, it could cause subsequent Read, Write, or Execute operations to target an unintended project. In the context of an MCP server with access to billing data and Spanner databases, setting the wrong project could misdirect sensitive operations.

From the tool's definition Tool name contains 'set' (modification operation); description states 'Set the default Google Cloud project ID to use for all operations' — this changes configuration state that affects downstream operations.

Documented attack patterns abuse exactly the kind of access gcp-utils-set-project-id gives an agent:

POLICY

How to control gcp-utils-set-project-id

PolicyLayer is an MCP gateway — it sits between your AI agents and Google Cloud MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for gcp-utils-set-project-id:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gcp-utils-set-project-id": {
      "limits": [
        {
          "counter": "gcp-utils-set-project-id_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

gcp-utils-set-project-id stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register Google Cloud MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Google Cloud MCP Server tools

Execute gcp-spanner-execute-query gcp-spanner-execute-query Execute gcp-spanner-query-count gcp-spanner-query-count Execute gcp-spanner-query-natural-language gcp-spanner-query-natural-language Read gcp-billing-analyse-costs Perform detailed cost analysis with trends and insights for Google Cloud billing data Read gcp-billing-cost-recommendations Generate cost optimisation recommendations with potential savings for Google Cloud billing Read gcp-billing-detect-anomalies Detect unusual cost patterns and spending anomalies in Google Cloud billing data Read gcp-billing-get-account-details Retrieve detailed information about a specific Google Cloud billing account Read gcp-billing-get-project-info Retrieve billing configuration and status for a Google Cloud project

All 40 Google Cloud MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about gcp-utils-set-project-id

What does the gcp-utils-set-project-id tool do? +

Set the default Google Cloud project ID to use for all operations. It is categorised as a Write tool in the Google Cloud MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on gcp-utils-set-project-id? +

Register the Google Cloud MCP Server MCP server in PolicyLayer and add a rule for gcp-utils-set-project-id: 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 MCP Server. Nothing to install.

What risk level is gcp-utils-set-project-id? +

gcp-utils-set-project-id is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit gcp-utils-set-project-id? +

Yes. Add a rate_limit block to the gcp-utils-set-project-id 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 gcp-utils-set-project-id completely? +

Set action: deny in the PolicyLayer policy for gcp-utils-set-project-id. 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 gcp-utils-set-project-id? +

gcp-utils-set-project-id is provided by the Google Cloud MCP Server MCP server (krzko/google-cloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Google Cloud MCP Server tool call.

Start from Google Cloud MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →