List all services in a cluster
AI agents call get_ecs_services to retrieve information from Ecs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and lists existing ECS services without creating, modifying, deleting, or executing any operations. It is a straightforward data retrieval function with minimal blast radius if misused by an agent—an attacker would only gain visibility into existing cluster configuration, not the ability to alter services or infrastructure.
From the tool's definition Tool name is 'get_ecs_services' and description states 'List all services in a cluster' — both indicate a read-only query operation with no data modification or side effects.
Documented attack patterns abuse exactly the kind of access get_ecs_services gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ecs, and nothing reaches the server without passing your rules. This is the rule we recommend for get_ecs_services:
{
"version": "1",
"default": "deny",
"tools": {
"get_ecs_services": {}
}
}get_ecs_services 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.
List all services in a cluster. It is categorised as a Read tool in the Ecs MCP Server, which means it retrieves data without modifying state.
Register the Ecs MCP server in PolicyLayer and add a rule for get_ecs_services: 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 Ecs. Nothing to install.
get_ecs_services 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 get_ecs_services 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 get_ecs_services. 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.
get_ecs_services is provided by the Ecs MCP server (neoai-agent/ecs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ecs, 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.
5 Ecs tools catalogued and risk-classified — across an index of 43,000+ MCP servers.