Updates a Timestream for InfluxDB DB instance.
AI agents use UpdateDbInstance 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 modifies an existing database instance's configuration or properties in a reversible manner (configurations can be changed again), making it a Write operation. Severity is high because unauthorized modifications to production database instances could cause service disruption, data accessibility issues, or performance degradation.
From the tool's definition Tool name 'UpdateDbInstance' combined with description 'Updates a Timestream for InfluxDB DB instance' indicates modification of database configuration or state. The verb 'Updates' explicitly signals write/modification operations.
Attacks that exploit this kind of access
Updates a Timestream for InfluxDB DB instance. 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 UpdateDbInstance: 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.
UpdateDbInstance 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 UpdateDbInstance 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 UpdateDbInstance. 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.
UpdateDbInstance 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.