execute_promql_query

// WHEN AI AGENTS USE THIS TOOL

AI agents invoke execute_promql_query to trigger processes or run actions in AWS Labs CloudWatch MCP Server. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

// WHY ENFORCE A POLICY ON EXECUTE_PROMQL_QUERY

execute_promql_query can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

// RECOMMENDED POLICY

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

aws-labs-cloudwatch-mcp-server.yaml

tools:
  execute_promql_query:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full AWS Labs CloudWatch MCP Server policy for all 19 tools.

// DETAILS

Tool Name execute_promql_query

Category Execute

MCP Server AWS Labs CloudWatch MCP Server MCP Server

Risk Level High

// MORE AWS LABS CLOUDWATCH MCP SERVER TOOLS

Destructive cancel_logs_insight_query Execute execute_cwl_insights_batch Execute execute_log_insights_query Execute execute_promql_range_query Read analyze_log_group Read analyze_metric Read describe_log_groups Read get_active_alarms

View all 19 tools →

// WHAT CAN GO WRONG

Agents calling execute-class tools like execute_promql_query have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER EXECUTE TOOLS ACROSS MCP SERVERS

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

Atv build_stake_tx Atv build_unstake_tx Acdp start_local Pentagonal pentagonal_audit Pentagonal pentagonal_compile ACR — Agent Composition Records orient_me

// IN CONTEXT OF HIGH RISK

execute_promql_query is one of the high-risk operations in AWS Labs CloudWatch MCP Server. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

// RELATED READING

// FAQ

What does the execute_promql_query tool do? +

Execute an instant PromQL query against CloudWatch. Returns the current value of metrics at a single point in time (instant vector). For time series over a range, use execute_promql_range_query instead. Use this tool when: - The user provides a PromQL expression - The user references OTLP-ingested metrics or labels (@resource.*, @aws.*, @instrumentation.*) - The user asks about enriched vended AWS metrics with OTel labels - The user wants to query by AWS resource tags (@aws.tag.*) Use get_metric_data instead when: - The user references classic CloudWatch namespaces/dimensions (AWS/EC2, etc.) - The user wants Metrics Insights SQL syntax PromQL label conventions (OTLP scope to label mapping): - @resource.{attr} - OTel resource attributes (e.g., @resource.service.name="myservice") - @instrumentation.{attr} - instrumentation scope (e.g., @instrumentation.@name="cloudwatch.aws/ec2") - @datapoint.{attr} or bare - datapoint attributes / CW dimensions (e.g., InstanceId="i-xxx") - @aws.account_id, @aws.region - AWS system labels - @aws.tag.{Key} - AWS resource tags (e.g., @aws.tag.Environment="production", @aws.tag.Team="backend") For enriched vended AWS metrics, use histogram functions (OTel enrichment must be enabled first: `aws cloudwatch start-otel-enrichment`): - histogram_avg({CPUUtilization, "@instrumentation.@name"="cloudwatch.aws/ec2"}) - histogram_sum({Invocations, FunctionName="my-func"}) Limits: max 500 series returned, 7-day range, 20s timeout. Example queries: - {"http.server.active_requests", "@resource.service.name"="myservice"} - histogram_avg({CPUUtilization, "@instrumentation.@name"="cloudwatch.aws/ec2"}) - sum by ("@aws.tag.Team")(histogram_sum({Invocations, "@instrumentation.@name"="cloudwatch.aws/lambda"})). It is categorised as a Execute tool in the AWS Labs CloudWatch MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_promql_query? +

Add a rule in your Intercept YAML policy under the tools section for execute_promql_query. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AWS Labs CloudWatch MCP Server MCP server.

What risk level is execute_promql_query? +

execute_promql_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit execute_promql_query? +

Yes. Add a rate_limit block to the execute_promql_query rule in your Intercept 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.

How do I block execute_promql_query completely? +

Set action: deny in the Intercept 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.

What MCP server provides execute_promql_query? +

execute_promql_query is provided by the AWS Labs CloudWatch MCP Server MCP server (awslabs.cloudwatch-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.