Get comprehensive service status including:
AI agents call check_ecs_service_status 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.
This tool retrieves and reports on the status of AWS ECS services without making any changes, triggering actions, or deleting data. It is a monitoring/querying capability with no side effects, fitting the Read category.
From the tool's definition Tool name 'check_ecs_service_status' and description 'Get comprehensive service status' indicates data retrieval with no modification or execution. Sibling tools (get_*) reinforce this pattern as read-only monitoring operations.
Documented attack patterns abuse exactly the kind of access check_ecs_service_status 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 check_ecs_service_status:
{
"version": "1",
"default": "deny",
"tools": {
"check_ecs_service_status": {}
}
}check_ecs_service_status 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 comprehensive service status including:. 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 check_ecs_service_status: 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.
check_ecs_service_status 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 check_ecs_service_status 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 check_ecs_service_status. 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.
check_ecs_service_status 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.