AI agents invoke execute_promql_query to trigger actions in Amazon ECS MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool name explicitly contains 'execute', which falls under the Execute category—running queries or commands whose effects depend on the query arguments. While PrometheusQL itself is typically read-only, the 'execute' designation and empty description create ambiguity about whether this tool could trigger operational changes, alerts, or external side effects.
From the tool's definition Tool name 'execute_promql_query' indicates execution of PrometheusQL queries. The 'execute' verb and context of an AWS ECS deployment server suggest runtime query execution against metrics systems.
Documented attack patterns abuse exactly the kind of access execute_promql_query 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 execute_promql_query:
{
"version": "1",
"default": "deny",
"tools": {
"execute_promql_query": {
"limits": [
{
"counter": "execute_promql_query_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}execute_promql_query stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
execute_promql_query. It is categorised as a Execute tool in the Amazon ECS MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Amazon ECS MCP Server MCP server in PolicyLayer and add a rule for execute_promql_query: 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.
execute_promql_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the execute_promql_query 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 execute_promql_query. 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.
execute_promql_query 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.