Retrieve information about AWS Support severity levels. This tool provides details about the available severity levels for AWS Support cases, including their codes and descriptions. ## Usage - You can request the response in either JSON or Markdown format. - Use this information to determine the...
Part of the AWS Support MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call describe_severity_levels to retrieve information from AWS Support 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 describe_severity_levels 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:
describe_severity_levels:
rules:
- action: allowSee the full AWS Support MCP Server policy for all 11 tools.
Agents calling read-class tools like describe_severity_levels 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.
Retrieve information about AWS Support severity levels. This tool provides details about the available severity levels for AWS Support cases, including their codes and descriptions. ## Usage - You can request the response in either JSON or Markdown format. - Use this information to determine the appropriate severity level for creating support cases. ## Example ``` describe_severity_levels() describe_severity_levels(language='ja', format='markdown') ``` ## Severity Level Guidelines - low (General guidance): You have a general development question or want to request a feature - normal (System impaired): Non-critical functions are behaving abnormally - high (Production system impaired): Important functions are impaired but a workaround exists - urgent (Production system down): Your business is significantly impacted; no workaround exists - critical (Business-critical system down): Your business is at risk; critical functions unavailable. It is categorised as a Read tool in the AWS Support 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 describe_severity_levels. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AWS Support MCP Server MCP server.
describe_severity_levels 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 describe_severity_levels 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 describe_severity_levels. 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.
describe_severity_levels is provided by the AWS Support MCP Server MCP server (awslabs.aws-support-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.