Create a new bucket in InfluxDB.
AI agents use InfluxDBCreateBucket to create or update resources in Awslabs Valkey — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Awslabs Valkey environment.
This tool creates a new bucket in InfluxDB, which is a data structure modification. Creating a bucket is reversible (it can be deleted), so it falls under Write rather than Destructive. The severity is medium because while bucket creation itself is not inherently high-risk, misconfiguration or creation of many buckets could impact system resources or data organization.
From the tool's definition Tool name 'InfluxDBCreateBucket' and description 'Create a new bucket in InfluxDB' indicate data creation. The action creates a new resource (bucket) in InfluxDB, which is a reversible operation typical of Write category tools.
Attacks that exploit this kind of access
Create a new bucket in InfluxDB. It is categorised as a Write tool in the Awslabs Valkey MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for InfluxDBCreateBucket: 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.
InfluxDBCreateBucket is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the InfluxDBCreateBucket 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 InfluxDBCreateBucket. 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.
InfluxDBCreateBucket 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.