Get all cached database connection information
AI agents call get_database_connection_info to retrieve information from Awslabs Valkey without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves database connection information, which is a read operation. However, connection information (hosts, ports, credentials, authentication details) is sensitive data that could enable unauthorized access if exposed to a malicious agent. While the action itself is non-destructive and non-modifying, the sensitivity of the data retrieved elevates severity to medium rather than low.
From the tool's definition The tool is named 'get_database_connection_info' and described as 'Get all cached database connection information', which indicates retrieval of existing data without modification or side effects.
Attacks that exploit this kind of access
Get all cached database connection information. It is categorised as a Read tool in the Awslabs Valkey MCP Server, which means it retrieves data without modifying state.
Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for get_database_connection_info: 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 Awslabs Valkey. Nothing to install.
get_database_connection_info 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 get_database_connection_info 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 get_database_connection_info. 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.
get_database_connection_info is provided by the Awslabs Valkey MCP server (awslabs.valkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.