List all Timestream for InfluxDB DB instances
AI agents call ListDbInstances 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 information about database instances without altering state. Listing resources is a read-only operation with no side effects. The low severity reflects that exposure would only leak metadata about existing infrastructure, not enable unauthorized modifications or destructive actions.
From the tool's definition Tool name 'ListDbInstances' and description 'List all Timestream for InfluxDB DB instances' indicate a list/query operation with no modification or deletion of data.
Attacks that exploit this kind of access
List all Timestream for InfluxDB DB instances. 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 ListDbInstances: 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.
ListDbInstances 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 ListDbInstances 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 ListDbInstances. 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.
ListDbInstances 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.