get_slo

// WHEN AI AGENTS USE THIS TOOL

AI agents call get_slo to retrieve information from CloudWatch Application Signals 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.

// WHY ENFORCE A POLICY ON GET_SLO

Even though get_slo 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.

// RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

cloudwatch-application-signals-mcp-server.yaml

tools:
  get_slo:
    rules:
      - action: allow

See the full CloudWatch Application Signals MCP Server policy for all 22 tools.

// DETAILS

Tool Name get_slo

Category Read

MCP Server CloudWatch Application Signals MCP Server MCP Server

Risk Level Low

// MORE CLOUDWATCH APPLICATION SIGNALS MCP SERVER TOOLS

Read analyze_canary_failures Read audit_group_health Read audit_service_operations Read audit_services Read audit_slos Read get_enablement_guide Read get_group_changes Read get_group_dependencies

View all 22 tools →

// WHAT CAN GO WRONG

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

Browse the full MCP Attack Database →

// OTHER READ TOOLS ACROSS MCP SERVERS

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

Firecrawl Web Scraping Server firecrawl_check_crawl_status Firecrawl Web Scraping Server firecrawl_crawl Firecrawl Web Scraping Server firecrawl_deep_research Firecrawl Web Scraping Server firecrawl_extract Firecrawl Web Scraping Server firecrawl_map Firecrawl Web Scraping Server firecrawl_scrape

// RELATED READING

// FAQ

What does the get_slo tool do? +

Get detailed information about a specific Service Level Objective (SLO). **RECOMMENDED WORKFLOW AFTER USING THIS TOOL:** After getting SLO configuration details, use `audit_slos()` with `auditors="all"` for comprehensive root cause analysis: - `audit_slos(slo_targets='[{"Type":"slo","Data":{"Slo":{"SloName":"your-slo-name"}}}]', auditors="all")` - This provides deep root cause analysis with traces, logs, metrics, and dependencies - Much more comprehensive than using individual trace tools Use this tool to: - Get comprehensive SLO configuration details - Understand what metrics the SLO monitors - See threshold values and comparison operators - Extract operation names and key attributes for further investigation - Identify dependency configurations - Review attainment goals and burn rate settings Returns detailed information including: - SLO name, description, and metadata - Metric configuration (for period-based or request-based SLOs) - Key attributes and operation names - Metric type (LATENCY or AVAILABILITY) - Threshold values and comparison operators - Goal configuration (attainment percentage, time interval) - Burn rate configurations This tool is essential for: - Understanding SLO configuration before deep investigation - Getting the exact SLO name/ARN for use with audit_slos() - Identifying the metrics and thresholds being monitored - Planning comprehensive root cause analysis workflow **NEXT STEP: Use audit_slos() with auditors="all" for root cause analysis**. It is categorised as a Read tool in the CloudWatch Application Signals MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_slo? +

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

What risk level is get_slo? +

get_slo is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_slo? +

Yes. Add a rate_limit block to the get_slo 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 get_slo completely? +

Set action: deny in the Intercept policy for get_slo. 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 get_slo? +

get_slo is provided by the CloudWatch Application Signals MCP Server MCP server (awslabs.cloudwatch-applicationsignals-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.