AI agents call aggregate as a supporting operation in Awslabs Valkey workflows.
The tool name 'aggregate' suggests some form of data aggregation, but without a description it's unclear what it does. In a Valkey/Redis context, aggregate operations typically read and compute over data (e.g., aggregating sorted sets or search results), suggesting a Read category. However, given the empty description, confidence is very low.
From the tool's definition Tool name is 'aggregate' and description is empty or uninformative.
Documented attack patterns abuse exactly the kind of access aggregate gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Awslabs Valkey, and nothing reaches the server without passing your rules. This is the rule we recommend for aggregate:
{
"version": "1",
"default": "deny",
"tools": {
"aggregate": {
"limits": [
{
"counter": "aggregate_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}aggregate gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
aggregate. It is categorised as a Other tool in the Awslabs Valkey MCP Server, which means it performs auxiliary operations.
Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for aggregate: 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.
aggregate is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the aggregate 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 aggregate. 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.
aggregate 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.
Start from Awslabs Valkey, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
805 Awslabs Valkey tools catalogued and risk-classified — across an index of 43,000+ MCP servers.