ThinAir Data

configure_allowlist

Destructive

Manage HARD SQL guardrails for an enterprise connection: a TABLE ALLOWLIST (queries may reference only the listed tables — enforced at the AST level across subqueries/CTEs/JOINs) and a PII MASKING policy (mask flagged columns in query results). Both opt-out by default. action=view shows current policy + schema reference; set_tables replaces the allowlist (use [] to lock down everything); remove_allowlist disables it; set_pii_policy toggles masking + chooses which PII kinds to mask. Masking is a heuristic policy aid (not a compliance guarantee) and one-way per execution. [ENTERPRISE tier]

Input Schema

TableJSON Schema

Name	Required	Description
`action`	Yes	What to do
`tables`	No	For set_tables: the allowlist. Bare ('users') or one-level schema-qualified ('public.users'). Empty array = lock down (no tables allowed).
`connection`	No	Target connection name from this tenant's inventory. Call `list_connections` to see every name + dialect. If the user didn't specify, use the tenant's default (first added). Do not invent names — resolve from `list_connections` output.
`pii_enabled`	No	For set_pii_policy: enable or disable result masking.
`mask_patterns`	No	For set_pii_policy: which PII kinds to mask (defaults to all when enabling without a list).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`meta`	No
`display`	No
`summary`	No
`insights`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 30, 2026

changedOutput schema / properties / data / anyOf

Previous value: -[
-  {
-    "additionalProperties": {},
-    "type": "object"
-  },
-  {
-    "additionalProperties": true,
-    "properties": {
-      "code": {
-        "type": "string"
-      },
-      "details": {
-        "additionalProperties": {},
-        "type": "object"
-      },
-      "error": {
-        "type": "string"
-      },
-      "internal_code": {
-        "type": "string"
-      },
-      "message": {
-        "type": "string"
-      },
-      "retry_after_s": {
-        "type": "number"
-      }
-    },
-    "required": [
-      "error"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "type": "object"
+  },
+  {
+    "additionalProperties": true,
+    "properties": {
+      "code": {
+        "type": "string"
+      },
+      "details": {
+        "additionalProperties": {},
+        "type": "object"
+      },
+      "error": {
+        "type": "string"
+      },
+      "internal_code": {
+        "type": "string"
+      },
+      "message": {
+        "type": "string"
+      },
+      "retry_after_s": {
+        "type": "number"
+      },
+      "retryable": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "error"
+    ],
+    "type": "object"
+  }
+]

addedOutput schema / properties / meta / properties / maskedCells
```
Added value: +{
+  "type": "number"
+}
```

addedOutput schema / properties / meta / properties / maskedColumns

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / meta / properties / rowCapReached
```
Added value: +{
+  "type": "boolean"
+}
```

Changed1 schema field changedSep 15, 2026

changedOutput schema / properties / data / anyOf

Previous value: -[
-  {
-    "additionalProperties": {},
-    "type": "object"
-  },
-  {
-    "additionalProperties": true,
-    "properties": {
-      "code": {
-        "type": "string"
-      },
-      "details": {
-        "additionalProperties": {},
-        "type": "object"
-      },
-      "error": {
-        "type": "string"
-      },
-      "internal_code": {
-        "type": "string"
-      },
-      "message": {
-        "type": "string"
-      },
-      "retry_after_s": {
-        "type": "number"
-      }
-    },
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "type": "object"
+  },
+  {
+    "additionalProperties": true,
+    "properties": {
+      "code": {
+        "type": "string"
+      },
+      "details": {
+        "additionalProperties": {},
+        "type": "object"
+      },
+      "error": {
+        "type": "string"
+      },
+      "internal_code": {
+        "type": "string"
+      },
+      "message": {
+        "type": "string"
+      },
+      "retry_after_s": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "error"
+    ],
+    "type": "object"
+  }
+]

AddedAug 17, 2026

TDQS

A4.3/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare destructiveHint=true and non-idempotent, and the description adds substantial context beyond them: AST-level enforcement across subqueries/CTEs/JOINs, empty array locking down all tables, masking being a heuristic aid rather than a compliance guarantee, one-way per-execution behavior, and the ENTREPRISE tier requirement.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense paragraph that front-loads the core concept before listing actions, with no filler sentences. The heavy parenthetical nesting reduces readability slightly but each clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a destructive, multi-action, enterprise-tier tool with an output schema (so return values need not be described) and 100% schema coverage, the description covers prerequisites, defaults, and safety caveats well. It omits any mention of auth/permission requirements for enterprise-tier use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so parameters are already documented in the schema. The description largely restates the action meanings and the [] locking semantics that the schema already provides, adding only the default-all-mask behavior, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (manage) over two named resources (table allowlist, PII masking policy) for an enterprise connection, and enumerates the four sub-actions with their effects. This clearly separates it from siblings like query_firewall or pii_scan.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains each action's purpose (view shows policy, set_tables replaces, remove_allowlist disables, set_pii_policy toggles masking) and notes both features are opt-out by default. It gives no explicit guidance on when to prefer this over pii_scan or query_firewall, which are adjacent siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ThinAir Data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?