This record as markdown: /tools/mozg31337-cloudstack-mcp-server/list-alerts.md
What list_alerts does on CloudStack MCP Server
AI agents call list_alerts to retrieve information from CloudStack MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_alerts is rated Low
The tool performs a simple data retrieval operation (list) on system alerts. There are no side effects, no code execution, no data modification, and no destructive operations. This is a straightforward Read category tool with low severity since viewing alerts poses minimal risk.
From the tool's definition Tool name 'list_alerts' and description 'List system alerts' indicate a read-only query operation that retrieves alert information without modifying, executing, or deleting any system state.
Attacks that exploit this kind of access
The rule that runs list_alerts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CloudStack MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_alerts, this is the rule to start with:
list_alerts is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect CloudStack MCP Server, apply this rule, and every list_alerts call is checked against it from then on.
Questions about list_alerts
List system alerts. It is categorised as a Read tool in the CloudStack MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for list_alerts: 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 CloudStack MCP Server. Nothing to install.
list_alerts 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_alerts 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_alerts. 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_alerts is provided by the CloudStack MCP Server MCP server (mozg31337/cloudstack-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CloudStack MCP Server, and thousands of servers like it.
This server
Across the catalogue