Monitor load balancer response times
AI agents call get_ecs_target_group_response_time 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 queries CloudWatch metrics related to load balancer response times. It performs read-only operations on existing monitoring data with no side effects, data modification, code execution, or destructive actions. The 'get_' prefix and 'Monitor' verb confirm it is a data retrieval function.
From the tool's definition Tool name contains 'get_' and description states 'Monitor load balancer response times', indicating retrieval and analysis of metrics without modification or execution of operations.
Documented attack patterns abuse exactly the kind of access get_ecs_target_group_response_time 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_target_group_response_time:
{
"version": "1",
"default": "deny",
"tools": {
"get_ecs_target_group_response_time": {}
}
} get_ecs_target_group_response_time 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.
Monitor load balancer response times. 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_target_group_response_time: 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_target_group_response_time 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_target_group_response_time 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_target_group_response_time. 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_target_group_response_time 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.