Diff the schemas of two databases (can be across different connections).
AI agents call compare_schemas to retrieve information from Querybridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
compare_schemas retrieves and compares structural metadata from two databases but does not create, modify, delete, or execute anything. It only reads schema information and presents differences. The blast radius of misuse is minimal—worst case an attacker learns schema structure of databases they may not have access to, but no data is compromised or altered.
From the tool's definition Tool performs a diff/comparison operation between two database schemas with no modification, deletion, or execution capabilities. The description states it 'diffs the schemas' which is a read-only analytical operation.
Attacks that exploit this kind of access
Diff the schemas of two databases (can be across different connections). It is categorised as a Read tool in the Querybridge MCP Server, which means it retrieves data without modifying state.
Register the Querybridge MCP server in PolicyLayer and add a rule for compare_schemas: 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 Querybridge. Nothing to install.
compare_schemas 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 compare_schemas 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 compare_schemas. 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.
compare_schemas is provided by the Querybridge MCP server (mahmoudhassanmustafa/querybridge-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 →