gcp-spanner-query-count

THE RISK

High Risk

Why gcp-spanner-query-count needs a policy

The tool name implies executing a COUNT query against a Google Cloud Spanner database. Database query execution can have significant blast radius if misused (e.g., expensive queries, exposure of sensitive data). However, the description is empty, so confidence is reduced. Given sibling tools and server context, this is most likely a read/execute operation on Spanner.

From the tool's definition Tool name 'gcp-spanner-query-count' and server description mentions 'interact with Spanner databases' — the word 'query' suggests executing a database query against Cloud Spanner

Documented attack patterns abuse exactly the kind of access gcp-spanner-query-count gives an agent:

POLICY

How to control gcp-spanner-query-count

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-spanner-query-count:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gcp-spanner-query-count": {
      "limits": [
        {
          "counter": "gcp-spanner-query-count_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

gcp-spanner-query-count 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.

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.

RATE-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-natural-language gcp-spanner-query-natural-language Write gcp-utils-set-project-id Set the default Google Cloud project ID to use for all operations 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 →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Google Cloud MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about gcp-spanner-query-count

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

gcp-spanner-query-count. It is categorised as a Execute tool in the Google Cloud 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-query-count? +

Register the Google Cloud MCP Server MCP server in PolicyLayer and add a rule for gcp-spanner-query-count: 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-spanner-query-count? +

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

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

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

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

gcp-spanner-query-count 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 →