AI agents call test_redshift_connection to retrieve information from Redshift MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Connection tests typically only attempt to establish and verify a database connection without reading, writing, or modifying any data. Given the empty description, confidence is reduced, but the name strongly implies a non-destructive ping/probe operation. Classified as Read at low severity since it likely returns connection status only.
From the tool's definition Tool name 'test_redshift_connection' suggests a connectivity check; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access test_redshift_connection gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Redshift MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for test_redshift_connection:
{
"version": "1",
"default": "deny",
"tools": {
"test_redshift_connection": {}
}
}test_redshift_connection is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
test_redshift_connection. It is categorised as a Read tool in the Redshift MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Redshift MCP Server MCP server in PolicyLayer and add a rule for test_redshift_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 Redshift MCP Server. Nothing to install.
test_redshift_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_redshift_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_redshift_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_redshift_connection is provided by the Redshift MCP Server MCP server (tuanknguyen/redshift-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Redshift MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Redshift MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.