Get enhanced recommendation details with integrated data from multiple AWS services.
AI agents call rec-details to retrieve information from Amazon ECS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves recommendation details by querying and aggregating data from multiple AWS services. It performs no mutations, executions, or destructive operations. However, the medium severity reflects that the aggregated recommendation data could expose sensitive architectural, security, or operational information about AWS infrastructure and applications, which could be valuable to an attacker for planning…
From the tool's definition Tool name 'rec-details' and description 'Get enhanced recommendation details with integrated data from multiple AWS services' indicate data retrieval only. The verb 'Get' and 'retrieval' pattern align with Read operations.
Documented attack patterns abuse exactly the kind of access rec-details gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon ECS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for rec-details:
{
"version": "1",
"default": "deny",
"tools": {
"rec-details": {}
}
} rec-details 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.
Get enhanced recommendation details with integrated data from multiple AWS services. It is categorised as a Read tool in the Amazon ECS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Amazon ECS MCP Server MCP server in PolicyLayer and add a rule for rec-details: 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 Amazon ECS MCP Server. Nothing to install.
rec-details 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 rec-details 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 rec-details. 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.
rec-details is provided by the Amazon ECS MCP Server MCP server (awslabs.ecs-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Amazon ECS 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 Amazon ECS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.