Get request count and error metrics
AI agents call get_ecs_target_group_request_metrics 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 queries monitoring data (request counts and error metrics) from AWS ECS target groups, consistent with CloudWatch metric retrieval. It has no side effects, does not execute code or commands, does not modify state, and does not involve financial transactions.
From the tool's definition Tool name contains 'get' and description states 'Get request count and error metrics' — purely a retrieval operation with no modification, deletion, or execution capability.
Documented attack patterns abuse exactly the kind of access get_ecs_target_group_request_metrics 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_request_metrics:
{
"version": "1",
"default": "deny",
"tools": {
"get_ecs_target_group_request_metrics": {}
}
}get_ecs_target_group_request_metrics 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 request count and error metrics. 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_request_metrics: 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_request_metrics 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_request_metrics 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_request_metrics. 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_request_metrics 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.