Low Risk

describe_support_cases

describe_support_cases

How to control describe_support_cases ↓

What describe_support_cases does on Awslabs Amazon Sns Sqs

AI agents call describe_support_cases to retrieve information from Awslabs Amazon Sns Sqs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why describe_support_cases needs a policy

The describe_* prefix strongly indicates a read-only operation that retrieves information about support cases. No description is provided, which lowers confidence slightly, but the naming convention and the presence of 'describe' in AWS APIs consistently maps to read operations. The low severity reflects that querying case metadata poses minimal risk even if misused by an agent.

From the tool's definition Tool name 'describe_support_cases' follows standard AWS API naming convention for read/query operations (describe_* pattern retrieves metadata without modification).

Documented attack patterns abuse exactly the kind of access describe_support_cases gives an agent:

How to control describe_support_cases

PolicyLayer is an MCP gateway — it sits between your AI agents and Awslabs Amazon Sns Sqs, and nothing reaches the server without passing your rules. This is the rule we recommend for describe_support_cases:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "describe_support_cases": {}
  }
}

describe_support_cases is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Awslabs Amazon Sns Sqs — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about describe_support_cases

What does the describe_support_cases tool do? +

describe_support_cases. It is categorised as a Read tool in the Awslabs Amazon Sns Sqs MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on describe_support_cases? +

Register the Awslabs Amazon Sns Sqs MCP server in PolicyLayer and add a rule for describe_support_cases: 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 Awslabs Amazon Sns Sqs. Nothing to install.

What risk level is describe_support_cases? +

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

Can I rate-limit describe_support_cases? +

Yes. Add a rate_limit block to the describe_support_cases 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.

How do I block describe_support_cases completely? +

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

describe_support_cases is provided by the Awslabs Amazon Sns Sqs MCP server (awslabs.amazon-sns-sqs-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Awslabs Amazon Sns Sqs tool call.

Start from Awslabs Amazon Sns Sqs, 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 Awslabs Amazon Sns Sqs tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.