Manage your personal library of reusable SELECT queries. action=save stores a query by name; action=run executes a saved query; action=list returns all your saved queries; action=delete removes one. [BUILD tier]
AI agents call saved_queries to permanently remove resources in ThinAir Data — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool spans multiple categories. The most severe applicable is Destructive because action=delete irreversibly removes a saved query. action=run also represents Execute risk since it executes stored SQL queries. action=save is Write. Per the rules, Destructive > Execute > Write, so Destructive is chosen.
From the tool's definition action=delete removes one [saved query]; action=save stores a query by name; action=run executes a saved query
Attacks that exploit this kind of access
Manage your personal library of reusable SELECT queries. action=save stores a query by name; action=run executes a saved query; action=list returns all your saved queries; action=delete removes one. [BUILD tier]. It is categorised as a Destructive tool in the ThinAir Data MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ThinAir Data MCP server in PolicyLayer and add a rule for saved_queries: 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.
saved_queries is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the saved_queries 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 saved_queries. 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.
saved_queries 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 →