query_firewall

Manage per-connection SQL rules: block dangerous patterns, require WHERE on large tables, log PII access. [ARCHITECT tier]

Server ThinAir Data thinairtelematics/thinair-data
Category Read
Risk class Low
Parameters 00 required

What query_firewall does on ThinAir Data

AI agents call query_firewall 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.

Why query_firewall needs a policy

Even though query_firewall only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Questions about query_firewall

What does the query_firewall tool do? +

Manage per-connection SQL rules: block dangerous patterns, require WHERE on large tables, log PII access. [ARCHITECT tier]. It is categorised as a Read tool in the ThinAir Data MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_firewall? +

Register the ThinAir Data MCP server in PolicyLayer and add a rule for query_firewall: 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.

What risk level is query_firewall? +

query_firewall is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit query_firewall? +

Yes. Add a rate_limit block to the query_firewall 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.

How do I block query_firewall completely? +

Set action: deny in the PolicyLayer policy for query_firewall. 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.

What MCP server provides query_firewall? +

query_firewall 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.