gcp-spanner-list-databases
AI agents call gcp-spanner-list-databases 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.
This tool lists Cloud Spanner databases, which is a read operation that retrieves information about existing resources without side effects. Confidence is slightly reduced (0.85 vs 0.95) because the tool description is empty, preventing definitive confirmation, but the name pattern and server context strongly indicate a read operation.
From the tool's definition Tool name 'gcp-spanner-list-databases' contains 'list', which typically retrieves or enumerates data without modification.
Attacks that exploit this kind of access
gcp-spanner-list-databases. 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-list-databases: 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-list-databases 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-list-databases 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-list-databases. 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-list-databases 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 →