gcp-spanner-query-count
AI agents call gcp-spanner-query-count to retrieve information from GCP Billing and Monitoring MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name implies a read/count operation on a Spanner database. 'Query' and 'count' typically indicate data retrieval without side effects. However, since the description is empty, there is uncertainty — a Spanner query tool could potentially execute arbitrary SQL including destructive statements. Confidence is lowered due to the lack of description.
From the tool's definition Tool name 'gcp-spanner-query-count' suggests counting/querying records in Google Cloud Spanner; description is empty and uninformative.
Attacks that exploit this kind of access
gcp-spanner-query-count. It is categorised as a Read tool in the GCP Billing and Monitoring MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GCP Billing and Monitoring 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 GCP Billing and Monitoring MCP Server. Nothing to install.
gcp-spanner-query-count is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
gcp-spanner-query-count 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →