List all buckets in InfluxDB.
AI agents call InfluxDBListBuckets 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 and lists existing buckets from InfluxDB without creating, modifying, or deleting any data. It is a read-only operation that has minimal blast radius if misused by an AI agent—it can only expose information about bucket names and metadata.
From the tool's definition Tool name 'InfluxDBListBuckets' and description 'List all buckets in InfluxDB' indicate a query/retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List all buckets in InfluxDB. 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 InfluxDBListBuckets: 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.
InfluxDBListBuckets 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 InfluxDBListBuckets 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 InfluxDBListBuckets. 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.
InfluxDBListBuckets 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.