list_alerts
Use this as the primary tool to list the alerts in a Google Cloud project. An alert is the representation of a violation of an alert policy. This is useful for understanding current and past violations of an alert policy.
This record as markdown: /tools/com-googleapis-monitoring-mcp/list-alerts.md
What list_alerts does on Mcp
AI agents call list_alerts to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
filter | string | — | Optional. An alert is returned if there is a match on any fields belonging to the alert or its subfields. |
parent | string | Yes | Required. The name of the project to list alerts for. |
orderBy | string | — | Optional. A comma-separated list of fields in `Alert` to use for sorting. The default sort direction is ascending. To specify descending order for a field, add |
pageSize | integer | — | Optional. The maximum number of results to return in a single response. If not set to a positive number, at most 50 alerts will be returned. The maximum value i |
pageToken | string | — | Optional. If non-empty, `page_token` must contain a value returned as the `next_page_token` in a previous response to request the next set of results. |
Parameters from the server's own tool schema.
Why list_alerts is rated Low
This tool retrieves and queries alert information from a Google Cloud project without creating, modifying, deleting, or executing any operations. It is purely informational, allowing visibility into existing alerts and policy violations. This is a standard Read operation with minimal risk if misused by an AI agent, as it only exposes existing alert data without capability to change infrastructure or trigger actions.
From the tool's definition Tool name is 'list_alerts' and description states it is used to 'list the alerts' and 'understanding current and past violations of an alert policy.' The verb 'list' and the read-only retrieval of alert data with no modification or side effects clearly…
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 Mcp, 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 Mcp, apply this rule, and every list_alerts call is checked against it from then on.
Questions about list_alerts
Use this as the primary tool to list the alerts in a Google Cloud project. An alert is the representation of a violation of an alert policy. This is useful for understanding current and past violations of an alert policy. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
list_alerts accepts 5 parameters: filter, parent, orderBy, pageSize, pageToken. Required: parent. The full parameter table on this page comes from the server's own tool schema.
Register the 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 Mcp. 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 MCP server (https://monitoring.googleapis.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue