Analyze the cost of a SQL query
AI agents call analyze_query_cost to retrieve information from BigQuery FinOps MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes cost metrics for a given query—a read-only operation that examines cost information without side effects. It does not execute the query itself, modify data, delete resources, or commit financial transactions. The analysis is informational only, making it a Read category tool with low severity.
From the tool's definition Tool name 'analyze_query_cost' and description 'Analyze the cost of a SQL query' indicate purely analytical inspection of query cost characteristics without execution or modification of data or financial systems.
Attacks that exploit this kind of access
Analyze the cost of a SQL query. It is categorised as a Read tool in the BigQuery FinOps MCP Server MCP Server, which means it retrieves data without modifying state.
Register the BigQuery FinOps MCP Server MCP server in PolicyLayer and add a rule for analyze_query_cost: 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 BigQuery FinOps MCP Server. Nothing to install.
analyze_query_cost 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 analyze_query_cost 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 analyze_query_cost. 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.
analyze_query_cost is provided by the BigQuery FinOps MCP Server MCP server (urfanazad/bq_azure_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 →