Ping a connection (SELECT 1) and return server version + latency. Fast way to confirm credentials and network path without running describe_schema.
AI agents call test_connection 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 is a simple connectivity test that retrieves minimal metadata (server version, latency) via a harmless SELECT statement. It has no destructive, write, or execute capabilities beyond basic diagnosis. The query is fixed and cannot be parameterized to cause harm. Blast radius is minimal—at worst, an AI agent confirms a database is reachable, which is low risk. Categorized as Read.
From the tool's definition Tool executes 'SELECT 1' and returns server version and latency—a read-only diagnostic query with no data modification or side effects. Description explicitly states it confirms credentials and network path without running schema operations.
Attacks that exploit this kind of access
Ping a connection (SELECT 1) and return server version + latency. Fast way to confirm credentials and network path without running describe_schema. 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 test_connection: 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.
test_connection 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 test_connection 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 test_connection. 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.
test_connection 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 →