Test database connection and return connection status
AI agents call check_connection to retrieve information from SQL Server MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool merely validates connectivity to the database and reports status. It retrieves information about the connection without creating, modifying, deleting, or executing any code or queries. This is a benign read operation with minimal blast radius even if called repeatedly or maliciously.
From the tool's definition Tool performs a connection status check with no modification, deletion, or execution capabilities. The description states it 'Test[s] database connection and return[s] connection status' — a purely diagnostic operation that queries the state of a connection…
Attacks that exploit this kind of access
Test database connection and return connection status. It is categorised as a Read tool in the SQL Server MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SQL Server MCP Server MCP server in PolicyLayer and add a rule for check_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 SQL Server MCP Server. Nothing to install.
check_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 check_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 check_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.
check_connection is provided by the SQL Server MCP Server MCP server (nebhg/sql-server-mcp). 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 →