gcp-spanner-execute-query

WHAT IT DOES

What gcp-spanner-execute-query does on GCP Billing and Monitoring MCP Server

AI agents invoke gcp-spanner-execute-query to trigger actions in GCP Billing and Monitoring MCP Server. 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 gcp-spanner-execute-query needs a policy

Despite the empty description limiting full context, the name 'execute-query' clearly indicates this tool runs SQL queries or similar commands against a database. This is an Execute category tool because it triggers external operations (database queries) whose effects depend on the query arguments.

From the tool's definition Tool name contains 'execute-query' which indicates code/query execution capability. Server description mentions 'querying' GCP services. The tool operates on Google Cloud Spanner (a distributed SQL database), making query execution a core function.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gcp-spanner-execute-query Rate-limited

gcp-spanner-execute-query 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": {
    "gcp-spanner-execute-query": {
      "limits": [
        {
          "counter": "gcp-spanner-execute-query_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 GCP Billing and Monitoring MCP Server, so you can run agents against it safely.

FAQ

Questions about gcp-spanner-execute-query

What does the gcp-spanner-execute-query tool do? +

gcp-spanner-execute-query. It is categorised as a Execute tool in the GCP Billing and Monitoring MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on gcp-spanner-execute-query? +

Register the GCP Billing and Monitoring MCP Server MCP server in PolicyLayer and add a rule for gcp-spanner-execute-query: 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 GCP Billing and Monitoring MCP Server. Nothing to install.

What risk level is gcp-spanner-execute-query? +

gcp-spanner-execute-query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit gcp-spanner-execute-query? +

Yes. Add a rate_limit block to the gcp-spanner-execute-query 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-spanner-execute-query completely? +

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

gcp-spanner-execute-query is provided by the GCP Billing and Monitoring MCP Server MCP server (radiumgu/gcp-billing-and-monitoring-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.