Creates a new Timestream for InfluxDB DB parameter group to associate with DB instances.
AI agents use CreateDbParamGroup 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 database parameter group, which is a reversible Write operation. It establishes configuration settings that can be updated or deleted without data loss. It does not execute arbitrary code, delete resources, move financial assets, or trigger irreversible changes.
From the tool's definition Creates a new Timestream for InfluxDB DB parameter group — the verb 'Creates' indicates the tool generates and persists new configuration resources that can be modified or deleted later.
Attacks that exploit this kind of access
Creates a new Timestream for InfluxDB DB parameter group to associate with DB instances. 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 CreateDbParamGroup: 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.
CreateDbParamGroup 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 CreateDbParamGroup 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 CreateDbParamGroup. 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.
CreateDbParamGroup 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.