test_database_connection
AI agents call test_database_connection to retrieve information from Universal SQL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though test_database_connection only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
test_database_connection. It is categorised as a Read tool in the Universal SQL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Universal SQL MCP Server MCP server in PolicyLayer and add a rule for test_database_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 Universal SQL MCP Server. Nothing to install.
test_database_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_database_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_database_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_database_connection is provided by the Universal SQL MCP Server MCP server (wunrry/universal-sql-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.