fetch_incidents
[Endpoint Detection and Response API 1.0] Returns a list of incidents. The endpoint is is designed for use by MDR vendors to retrieve incidents for their customers and store them on their backend for future use. It is not intended for building UIs or for direct user interaction. Usage is quota-li...
This record as markdown: /tools/acronis-platform-mcp/fetch-incidents.md
What fetch_incidents does on Acronis Platform
AI agents call fetch_incidents to retrieve information from Acronis Platform 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 |
|---|---|---|---|
query | object | — | Query parameters |
Parameters from the server's own tool schema.
Why fetch_incidents is rated Low
Even though fetch_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.
Risk signalsHigh parameter count (19 properties)
Attacks that exploit this kind of access
The rule that runs fetch_incidents safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Acronis Platform, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fetch_incidents, this is the rule to start with:
fetch_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 Acronis Platform, apply this rule, and every fetch_incidents call is checked against it from then on.
Questions about fetch_incidents
[Endpoint Detection and Response API 1.0] Returns a list of incidents. The endpoint is is designed for use by MDR vendors to retrieve incidents for their customers and store them on their backend for future use. It is not intended for building UIs or for direct user interaction. Usage is quota-limited based on the size of the result set. It is categorised as a Read tool in the Acronis Platform MCP Server, which means it retrieves data without modifying state.
fetch_incidents accepts 1 parameter: query. The full parameter table on this page comes from the server's own tool schema.
Register the Acronis Platform MCP server in PolicyLayer and add a rule for fetch_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 Acronis Platform. Nothing to install.
fetch_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 fetch_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 fetch_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.
fetch_incidents is provided by the Acronis Platform MCP server (@acronis-platform/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Acronis Platform, and thousands of servers like it.
This server
Across the catalogue