AI agents call aggregate to retrieve information from AWS Well-Architected Security Assessment Tool MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name suggests data aggregation rather than state modification. Without a description, confidence is reduced, but the semantic context of an assessment/analysis tool and the absence of action verbs (create, delete, execute) indicate a Read operation. Lower severity assigned due to informational nature and low confidence due to missing documentation.
From the tool's definition Tool name 'aggregate' lacks description. Based on naming convention in Well-Architected context, likely aggregates or summarizes data from assessments without modifying state.
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 AWS Well-Architected Security Assessment Tool MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for aggregate:
{
"version": "1",
"default": "deny",
"tools": {
"aggregate": {}
}
}aggregate is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
All 805 AWS Well-Architected Security Assessment Tool MCP Server tools →
aggregate. It is categorised as a Read tool in the AWS Well-Architected Security Assessment Tool MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AWS Well-Architected Security Assessment Tool MCP Server 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 AWS Well-Architected Security Assessment Tool MCP Server. Nothing to install.
aggregate is a Read 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 AWS Well-Architected Security Assessment Tool MCP Server MCP server (awslabs.well-architected-security-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS Well-Architected Security Assessment Tool MCP Server, 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 AWS Well-Architected Security Assessment Tool MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.