get_cloud_incidents
Use this when the user wants to check for active cloud platform outages, service disruptions, or incidents from AWS or Google Cloud. Both active and archived incidents are included unless status is filtered. Do NOT use this for cost anomalies (use get_anomalies) or support tickets (use list_ticke...
This record as markdown: /tools/doit/get-cloud-incidents.md
What get_cloud_incidents does on Doit
AI agents call get_cloud_incidents 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 filters in format key:value|key:value. Keys: platform (amazon-web-services or google-cloud), status (active or archived), product. Different keys use AND; |
platform | object | — | Platform constraint: amazon-web-services or google-cloud. Legacy google-cloud-project is normalized to google-cloud. If filter also contains platform, it must s |
pageToken | string | — | Token for pagination, from a previous response; returns the next page of results. |
Parameters from the server's own tool schema.
Why get_cloud_incidents is rated Low
Even though get_cloud_incidents 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 get_cloud_incidents 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 get_cloud_incidents, this is the rule to start with:
get_cloud_incidents 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 get_cloud_incidents call is checked against it from then on.
Questions about get_cloud_incidents
Use this when the user wants to check for active cloud platform outages, service disruptions, or incidents from AWS or Google Cloud. Both active and archived incidents are included unless status is filtered. Do NOT use this for cost anomalies (use get_anomalies) or support tickets (use list_tickets). It is categorised as a Read tool in the Doit MCP Server, which means it retrieves data without modifying state.
get_cloud_incidents accepts 3 parameters: filter, platform, pageToken. 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 get_cloud_incidents: 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.
get_cloud_incidents 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 get_cloud_incidents 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 get_cloud_incidents. 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.
get_cloud_incidents 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