configure_domain
AI agents use configure_domain 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.
Domain configuration in ElastiCache/MemoryDB is a reversible Write operation—it modifies cluster settings (SSL, encryption, network domains) without deleting data. The high severity reflects that misconfigured domains could disable access, break encryption, or expose clusters. Confidence is moderate due to empty description, but the name and AWS service context indicate clear data/configuration modification intent.
From the tool's definition Tool name 'configure_domain' indicates configuration modification. Given the context of AWS ElastiCache/MemoryDB Valkey, domain configuration changes would modify network/SSL settings and other cluster properties. Description is empty, limiting certainty.
Attacks that exploit this kind of access
configure_domain. 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 configure_domain: 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.
configure_domain 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 configure_domain 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 configure_domain. 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.
configure_domain 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.