Check the Redshift connection status.
AI agents call redshift_connection_status 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.
This tool only retrieves status information about an existing connection. It has no side effects, does not execute queries, modify data, or perform destructive operations. It is a simple diagnostic/monitoring operation that falls squarely into the Read category with low severity.
From the tool's definition Tool name 'redshift_connection_status' and description 'Check the Redshift connection status' indicate a read-only operation that queries connection status without modifying any data.
Attacks that exploit this kind of access
Check the Redshift connection status. 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 redshift_connection_status: 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.
redshift_connection_status 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 redshift_connection_status 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 redshift_connection_status. 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.
redshift_connection_status is provided by the Redshift MCP Server MCP server (santosh07401/redshift-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 →