Low Risk

get_active_alarms

get_active_alarms

How to control get_active_alarms ↓

What get_active_alarms does on Awslabs Amazon Sns Sqs

AI agents call get_active_alarms 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 get_active_alarms needs a policy

The 'get_' prefix and 'active_alarms' noun strongly suggest this tool retrieves alarm state information without modification. Despite the empty description limiting confidence, retrieval of alarm status has no side effects and minimal blast radius if misused by an agent. Classified as Read/low severity.

From the tool's definition Tool name 'get_active_alarms' indicates a retrieval operation; the prefix 'get_' is a standard Read operation pattern. Tool description is empty, reducing specificity.

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

How to control get_active_alarms

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 get_active_alarms:

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

get_active_alarms 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 get_active_alarms

What does the get_active_alarms tool do? +

get_active_alarms. 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 get_active_alarms? +

Register the Awslabs Amazon Sns Sqs MCP server in PolicyLayer and add a rule for get_active_alarms: 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 get_active_alarms? +

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

Can I rate-limit get_active_alarms? +

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

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

get_active_alarms 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.