bulk_update_investigation_state
[Endpoint Detection and Response API 1.0] Post update for an investigation state accompanied with comment or post a new comment for multiple incidents by MDR vendor.
This record as markdown: /tools/acronis-platform-mcp/bulk-update-investigation-state.md
What bulk_update_investigation_state does on Acronis Platform
AI agents use bulk_update_investigation_state to create or update resources in Acronis Platform, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Acronis Platform environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | object | — | Request body (JSON object) |
query | object | — | Query parameters |
headers | object | — | Request headers |
Parameters from the server's own tool schema.
Why bulk_update_investigation_state is rated Medium
An AI agent can call bulk_update_investigation_state faster than any human can review: one bad instruction and it creates or modifies resources in Acronis Platform by the hundred, each call as confident as the last.
Risk signalsAccepts raw HTML/template content (body) · High parameter count (19 properties) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs bulk_update_investigation_state 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 bulk_update_investigation_state, this is the rule to start with:
bulk_update_investigation_state stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 bulk_update_investigation_state call is checked against it from then on.
Questions about bulk_update_investigation_state
[Endpoint Detection and Response API 1.0] Post update for an investigation state accompanied with comment or post a new comment for multiple incidents by MDR vendor. It is categorised as a Write tool in the Acronis Platform MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
bulk_update_investigation_state accepts 3 parameters: body, query, headers. 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 bulk_update_investigation_state: 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.
bulk_update_investigation_state is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the bulk_update_investigation_state 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 bulk_update_investigation_state. 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.
bulk_update_investigation_state 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