AI agents invoke gcp-spanner-execute-query to trigger actions in Google Cloud 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.
The tool's name 'execute-query' combined with its context (Spanner database interaction) indicates it runs arbitrary SQL queries. Without description text to confirm scope limitations, the most reasonable interpretation is that it can execute any valid SQL statement.
From the tool's definition Tool name includes 'execute-query' in the context of a Spanner database tool. Spanner is a relational database, and 'execute-query' on a database typically permits running arbitrary SQL statements including SELECT, INSERT, UPDATE, DELETE, and DDL operations.
Documented attack patterns abuse exactly the kind of access gcp-spanner-execute-query gives an agent:
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-execute-query:
{
"version": "1",
"default": "deny",
"tools": {
"gcp-spanner-execute-query": {
"limits": [
{
"counter": "gcp-spanner-execute-query_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
gcp-spanner-execute-query. 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.
Register the Google Cloud 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 Google Cloud MCP Server. Nothing to install.
gcp-spanner-execute-query 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 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.
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.
gcp-spanner-execute-query 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.
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.
Free to start. No card required.
40 Google Cloud MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.