AI agents call test_connection to retrieve information from Mssql without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
connectionName | string | — | Named connection to use (e.g., 'production', 'staging') |
connectionString | string | — | SQL Server connection string (uses default if not provided) |
Parameters from the server's own tool schema.
This tool performs a connection test and retrieves basic server metadata. It has no side effects, does not execute arbitrary code, does not modify data, and does not delete anything. It is purely informational, similar to a ping or status check. The blast radius of misuse is minimal—an attacker could only learn basic server details already available to authenticated users.
From the tool's definition Tool name 'test_connection' and description 'Test the database connection and return basic server information' indicate a non-destructive query operation that retrieves diagnostic information without modifying data.
Attacks that exploit this kind of access
Test the database connection and return basic server information. It is categorised as a Read tool in the Mssql MCP Server, which means it retrieves data without modifying state.
test_connection accepts 2 parameters: connectionName, connectionString. The full parameter table on this page comes from the server's own tool schema.
Register the Mssql 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 Mssql. 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 Mssql MCP server (mssql-mcp-server). 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 →