Gets metadata for a CloudWatch metric including description, unit and recommended statistics that can be used for metric data retrieval. This tool retrieves comprehensive metadata about a specific CloudWatch metric identified by its namespace and metric name. Note: This function uses local metad...
Single-target operation
Part of the AWS Labs CloudWatch MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call get_metric_metadata to retrieve information from AWS Labs CloudWatch MCP Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_metric_metadata only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
get_metric_metadata:
rules:
- action: allowSee the full AWS Labs CloudWatch MCP Server policy for all 19 tools.
Agents calling read-class tools like get_metric_metadata have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Gets metadata for a CloudWatch metric including description, unit and recommended statistics that can be used for metric data retrieval. This tool retrieves comprehensive metadata about a specific CloudWatch metric identified by its namespace and metric name. Note: This function uses local metadata and does not make AWS API calls. Usage: Use this tool to get detailed information about CloudWatch metrics, including their descriptions, units, and recommended statistics to use. Args: ctx: The MCP context object for error handling and logging. namespace: The metric namespace (e.g., "AWS/EC2", "AWS/Lambda") metric_name: The name of the metric (e.g., "CPUUtilization", "Duration") Returns: Optional[MetricMetadata]: An object containing the metric's description, recommended statistics, and unit if found, None if no metadata is available. Example: result = await get_metric_metadata( ctx, namespace="AWS/EC2", metric_name="CPUUtilization" ) if result: print(f"Description: {result.description}") print(f"Unit: {result.unit}") print(f"Recommended Statistics: {result.recommendedStatistics}"). It is categorised as a Read tool in the AWS Labs CloudWatch MCP Server MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for get_metric_metadata. 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.
get_metric_metadata 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_metric_metadata 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.
Set action: deny in the Intercept policy for get_metric_metadata. 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_metric_metadata 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.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.