Analyze historical query performance patterns and provide optimization recommendations with cost insights.
AI agents call analyze_query_performance to retrieve information from MCP BigQuery 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 historical query performance patterns to offer insights and recommendations. It has no side effects—no data is created, modified, deleted, or executed. The cost insights are informational outputs derived from analysis. While it operates on potentially sensitive performance metadata, the actual operation is fundamentally a read/query operation with analysis.
From the tool's definition The tool 'analyze_query_performance' performs analysis and provides recommendations based on historical data.
Attacks that exploit this kind of access
Analyze historical query performance patterns and provide optimization recommendations with cost insights. It is categorised as a Read tool in the MCP BigQuery Server MCP Server, which means it retrieves data without modifying state.
Register the MCP BigQuery Server MCP server in PolicyLayer and add a rule for analyze_query_performance: 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 MCP BigQuery Server. Nothing to install.
analyze_query_performance 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_performance 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_performance. 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_performance is provided by the MCP BigQuery Server MCP server (mousten/mcp-bigquery-server). 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 →