Track schema evolution and changes over time for specific tables with impact analysis.
AI agents call get_schema_changes 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 displays schema change history and performs read-only analysis. It does not execute queries, modify data structures, delete records, or trigger external operations. The 'impact analysis' refers to analyzing consequences of past changes, not performing destructive or side-effect operations. No financial, executable, or destructive capabilities are present.
From the tool's definition Tool name 'get_schema_changes' and description 'Track schema evolution and changes over time for specific tables with impact analysis' indicate querying historical metadata without modifying data or executing operations.
Attacks that exploit this kind of access
Track schema evolution and changes over time for specific tables with impact analysis. 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 get_schema_changes: 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.
get_schema_changes 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 get_schema_changes 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 get_schema_changes. 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.
get_schema_changes 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 →