AI agents call test_connection to retrieve information from Mcp Odbc without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries connection metadata (DBMS type and version) without side effects. It is a read-only diagnostic operation. While the server offers write access per-connection, this specific tool does not write or execute queries. The low severity reflects minimal blast radius: connection testing poses no risk of data loss, code execution, or resource exhaustion beyond normal connection overhead.
From the tool's definition Tool performs a connection test to report DBMS type and version. No data retrieval, modification, execution, or deletion occurs. The description explicitly states it 'test[s]' and 'report[s]' — diagnostic/informational operations only.
Attacks that exploit this kind of access
Test an ODBC connection and report DBMS type and version. It is categorised as a Read tool in the Mcp Odbc MCP Server, which means it retrieves data without modifying state.
Register the Mcp Odbc 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 Mcp Odbc. 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 Mcp Odbc MCP server (phil-cheesman/mcp-odbc). 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 →