mist_list_alarms

List recent Mist site alarms with compact severity/time fields.

SERVERAPI-Central SOURCEsecure-ssid/centralmcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/secure-ssid-centralmcp/mist-list-alarms.md

WHAT IT DOES

What mist_list_alarms does on API-Central

AI agents call mist_list_alarms to retrieve information from API-Central without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why mist_list_alarms is rated Low

This tool retrieves and displays existing alarm information from a Mist site monitoring system. It performs a read-only query operation that returns alarm data in a compact format. There is no data creation, modification, deletion, code execution, or financial impact. The blast radius of misuse is minimal—an agent could retrieve alarm information but cannot act upon it to cause harm.

From the tool's definition Tool name 'mist_list_alarms' with verb 'list' and description 'List recent Mist site alarms' indicates retrieval of alarm data with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mist_list_alarms safely

PolicyLayer is an MCP gateway: it sits between your AI agents and API-Central, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mist_list_alarms, this is the rule to start with:

mist_list_alarms Allowed

mist_list_alarms is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mist_list_alarms": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect API-Central, apply this rule, and every mist_list_alarms call is checked against it from then on.

FAQ

Questions about mist_list_alarms

What does the mist_list_alarms tool do? +

List recent Mist site alarms with compact severity/time fields. It is categorised as a Read tool in the API-Central MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mist_list_alarms? +

Register the API-Central MCP server in PolicyLayer and add a rule for mist_list_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 API-Central. Nothing to install.

What risk level is mist_list_alarms? +

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

Can I rate-limit mist_list_alarms? +

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

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

mist_list_alarms is provided by the API-Central MCP server (secure-ssid/centralmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on API-Central, and thousands of servers like it.

This server

All 590 API-Central tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →