list_alarms
AI agents call list_alarms to retrieve information from Yamcs MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list_alarms' tool appears to query or retrieve alarm records from a Yamcs mission control system. Listing operations are read-only queries with no side effects on the underlying data. Despite the empty description reducing confidence slightly, the semantic meaning of 'list' combined with the broader server context (telemetry and monitoring) indicates this is a retrieval tool with low blast radius if misused.
From the tool's definition Tool name 'list_alarms' indicates a listing operation that retrieves alarm data without modification. The empty description is uninformative, but the naming convention and context within a mission control system strongly suggests this is a data retrieval…
Attacks that exploit this kind of access
list_alarms. It is categorised as a Read tool in the Yamcs MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Yamcs MCP Server MCP server in PolicyLayer and add a rule for 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 Yamcs MCP Server. Nothing to install.
list_alarms 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 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.
Set action: deny in the PolicyLayer policy for 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.
list_alarms is provided by the Yamcs MCP Server MCP server (paulmramirez/yamcs-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →