Execute a read-only SQL query against the target connection. ONLY SELECT / WITH / EXPLAIN permitted. Write dialect-appropriate SQL for the connection
AI agents call query_sql to retrieve information from ThinAir Data without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool explicitly restricts execution to read-only SQL statements (SELECT, WITH, EXPLAIN), making it a Read category tool. Severity is medium rather than low because even read-only SQL queries can expose sensitive data at scale across PostgreSQL, MySQL, or SQL Server databases, and a misconfigured or malicious query could exfiltrate large volumes of data.
From the tool's definition Execute a read-only SQL query... ONLY SELECT / WITH / EXPLAIN permitted
Attacks that exploit this kind of access
Execute a read-only SQL query against the target connection. ONLY SELECT / WITH / EXPLAIN permitted. Write dialect-appropriate SQL for the connection. It is categorised as a Read tool in the ThinAir Data MCP Server, which means it retrieves data without modifying state.
Register the ThinAir Data MCP server in PolicyLayer and add a rule for query_sql: 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 ThinAir Data. Nothing to install.
query_sql 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 query_sql 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 query_sql. 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.
query_sql is provided by the ThinAir Data MCP server (thinairtelematics/thinair-data). 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 →