List every database connection registered for your tenant: name, id, dbType (postgres / mysql / mssql), createdAt. Flags duplicate names. Returns nothing sensitive (no DSN, no credentials).
AI agents call list_connections 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.
This tool retrieves metadata about database connections without exposing sensitive authentication details or enabling modifications. It is purely informational—listing connection names, IDs, database types, and creation timestamps. No data is modified, no code is executed, and no sensitive credentials are exposed. This is a standard read/list operation with minimal risk.
From the tool's definition Tool description states it 'List[s] every database connection registered' and explicitly confirms 'Returns nothing sensitive (no DSN, no credentials).' The tool performs query and retrieval operations only.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List every database connection registered for your tenant: name, id, dbType (postgres / mysql / mssql), createdAt. Flags duplicate names. Returns nothing sensitive (no DSN, no credentials). 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 list_connections: 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.
list_connections 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 list_connections 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 list_connections. 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.
list_connections 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 →