list_alerts
Use this when the user wants to see their cost alerts or check alert configurations. Returns a paginated list of alerts. Do NOT use this for anomaly detection (use get_anomalies) or budget tracking (use list_budgets).
This record as markdown: /tools/doit/list-alerts.md
What list_alerts does on Doit
AI agents call list_alerts to retrieve information from Doit 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 | — | Exact, case-sensitive filters: owner (email) or name. Use key:value and join distinct keys with | (AND). Repeated keys are rejected. Example: owner:user@example |
sortBy | string | — | A field by which the results will be sorted. |
pageToken | string | — | Page token returned by a previous call to request the next page of results. |
sortOrder | string | — | Sort order: ascending (asc) or descending (desc). |
maxResults | string | — | Maximum results per page. Tool default 40; valid range 1–500. Out-of-range values fall back to 50 at the API. |
Parameters from the server's own tool schema.
Why list_alerts is rated Low
Even though list_alerts only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
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 Doit, 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 Doit, apply this rule, and every list_alerts call is checked against it from then on.
Questions about list_alerts
Use this when the user wants to see their cost alerts or check alert configurations. Returns a paginated list of alerts. Do NOT use this for anomaly detection (use get_anomalies) or budget tracking (use list_budgets). It is categorised as a Read tool in the Doit MCP Server, which means it retrieves data without modifying state.
list_alerts accepts 5 parameters: filter, sortBy, pageToken, sortOrder, maxResults. The full parameter table on this page comes from the server's own tool schema.
Register the Doit 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 Doit. 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 Doit MCP server (@doitintl/doit-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Doit, and thousands of servers like it.
This server
Across the catalogue