Acronis MCP Tools & API Patterns
Overview
Acronis Cyber Protect Cloud is a multi-tenant backup, disaster recovery and
endpoint protection platform. MSPs run it as a partner tenant with one
customer tenant per client. The Conduit connector wraps Acronis's own MCP
server and exposes a curated set of 37 tools. Tool names are acronis_ plus
the Acronis operation name, such as acronis_fetch_all_alerts.
Connection & Authentication
Conduit sends three headers to the Acronis connector:
| Header |
Conduit field |
Value |
X-Acronis-Base-Url |
Data center URL |
The data center Acronis shows when you create the API client, such as https://us5-cloud.acronis.com. Origin only: nothing after .com. |
X-Acronis-Client-Id |
Client ID |
The API client's ID |
X-Acronis-Client-Secret |
Client Secret |
The API client's secret |
You enter these fields once in the Conduit web UI (/connect/acronis).
Conduit stores them and injects the headers on every request; nothing is set
on the client, and Conduit drops any X-Acronis-* header a client sends.
How to get them:
- In the Acronis management portal, open Settings → API clients.
- Create an API client. Copy the Client ID, the Secret and the data center
URL that Acronis shows. The secret is only shown once.
- Don't use your Acronis portal email and password. Conduit needs an API
client, which signs in with the OAuth
client_credentials flow.
When you connect, Conduit checks the data center URL (it must be https on an
acronis.com host) and does a real token exchange with Acronis, so a wrong
secret or the wrong data center fails at connect time, not on the first tool
call.
What the connection can see
- Everyone in your Conduit org shares this one connection.
- The API client sees only the tenant that owns it and the tenants under it.
An API client created in the partner tenant sees every customer. One created
inside a customer tenant sees only that customer.
Tenant Hierarchy
Partner (the MSP) → [Folder] → Customer (a client) → [Unit]
Almost every read filters by a tenant UUID. The parameter name differs by API
family, which is the most common source of empty results:
| API family |
Tenant parameter |
| Account management (tenants, users, usage, MFA) |
tenant_id in path, or parent_id / subtree_root_id / uuids in query |
| Alerts |
tenant (an array) in query; per-customer tools use customer_id |
| Policies, resources, protection status |
tenant_id in query |
| Agents |
tenant_id in query, meaning a subtree root |
| EDR incidents |
customer_id in query |
Tool Surface
All tools are listed directly. There is no navigation step.
| Area |
Tools |
| Tenants and users |
acronis_fetch_tenant, acronis_fetch_tenants_batch, acronis_fetch_tenant_children, acronis_fetch_tenant_users, acronis_fetch_users_batch, acronis_fetch_user, acronis_fetch_current_user_info, acronis_search, acronis_fetch_tenant_mfa_status, acronis_fetch_tenant_usages |
| Alerts |
acronis_fetch_all_alerts, acronis_fetch_alert, acronis_fetch_categories, acronis_fetch_alert_counters, acronis_fetch_alerts_grouped_by_scope, acronis_fetch_all_alert_types, acronis_fetch_resources_with_top_severity_alerts, acronis_fetch_alert_counts_per_customer, acronis_fetch_alerts_grouped_per_customer, acronis_fetch_active_alert_count |
| Protection policies (protection plans) |
acronis_fetch_policies, acronis_fetch_policy, acronis_fetch_policy_applications, acronis_fetch_applications_issue_statistics, acronis_fetch_application_statuses_by_policy |
| Resources (machines, mailboxes, workloads) |
acronis_fetch_resources, acronis_fetch_resource_count, acronis_fetch_resource, acronis_fetch_resource_protection_status |
| Agents |
acronis_fetch_agents, acronis_fetch_agent |
| EDR incidents |
acronis_fetch_incidents, acronis_fetch_incident, acronis_fetch_response_action_status |
| Writes (off by default) |
acronis_mark_alert_as_false_positive, acronis_update_investigation_state, acronis_execute_protection_policy |
Writes and Conduit permission tiers
The three write tools are off by default. They don't appear in the tool
list until WYRE turns writes on for the Acronis connector. When they are on,
Conduit gates them by permission tier:
| Tool |
Conduit tier |
What it changes |
| All 34 reads |
read |
Nothing |
acronis_mark_alert_as_false_positive |
write |
Sets or clears the false-positive flag on an alert, for everyone in Acronis |
acronis_update_investigation_state |
write |
Changes an EDR incident's investigation state or adds a comment |
acronis_execute_protection_policy |
admin |
Runs a protection plan now on every machine it covers, starting backup or protection jobs |
If a write tool is missing from the tool list, writes are off. Say so plainly
and give the operator the console path instead of looking for a workaround.
Not available through this connector
Creating or deleting tenants, users or API clients, any delete, pricing and
offering items, registration tokens, branding, and starting EDR response
actions (such as isolating a machine) are not exposed at all. Reading the
status of a response action that was started in the console is available
through acronis_fetch_response_action_status.
Argument Shape
Arguments are grouped the way the Acronis REST API groups them: path for
URL path parameters, query for query-string filters, and body for write
payloads. A few tools also take headers.
{
"path": { "tenant_id": "0f8fad5b-d9cb-469f-a165-70867728950e" },
"query": { "embed_path": true }
}
Tenant, user and policy IDs are lowercase UUIDs. Several filters take a
comma-separated list of up to 100 UUIDs in one string, such as uuids on
acronis_fetch_tenants_batch and tenant_id on acronis_fetch_resources.
Pagination
Each Acronis API family pages differently. Check for a next cursor before you
say a list is complete.
| Tools |
How to page |
acronis_fetch_tenants_batch, acronis_fetch_users_batch, acronis_fetch_tenant_children |
limit plus after. Read the next cursor from paging.cursors.after. The cursor carries the filters, so pass only after on later pages. |
acronis_fetch_policies, acronis_fetch_policy_applications, acronis_fetch_application_statuses_by_policy, acronis_fetch_resources, acronis_fetch_resource_protection_status |
limit plus after / before cursors |
acronis_fetch_agents |
limit plus after / before. Leaving limit out or setting it to 0 returns every agent, which can hit the response size cap. |
acronis_fetch_incidents |
limit plus cursor. Every other filter and the sort order must stay exactly the same between pages. |
acronis_fetch_all_alerts |
No cursor. limit caps the result. Narrow with filters (tenant, category, severity, created_at) and use skip to leave out alert IDs you've already seen. |
For counts, use the count tools instead of paging: acronis_fetch_resource_count,
acronis_fetch_alert_counters, acronis_fetch_alert_counts_per_customer and
acronis_fetch_active_alert_count.
Filter Syntax
- Alerts use operator functions:
severity: "or(warning,critical)",
severity: "gt(warning)", planName: ["eq(Daily backup)"]. A bare
planName or resourceName value matches a substring. IDs passed with
or(...) match exactly.
- Alert timestamps (
created_at, updated_at, deleted_at) are Unix
time in nanoseconds, with an operator:
created_at: "gt(1793491200000000000)" means after 2026-11-01 00:00 UTC.
Seconds or milliseconds silently match nothing useful.
- EDR incidents use
range(date_from, date_to) and ge(date_from) for
created_at / updated_at, and or(a,b) for state, severity and
mitigation_state.
- Policies and resources take a
search string with an SQL-like syntax
over name, type and tags.
Errors
The connector returns errors as JSON:
{ "error": { "code": "upstream_unavailable", "message": "..." } }
Messages are capped at 500 characters and never contain the client secret.
| Symptom |
Cause |
What to do |
upstream_unavailable |
The connector could not start a session with Acronis: the API client was disabled or its secret rotated, or the data center can't be reached |
Re-check the API client under Settings → API clients and reconnect Acronis in Conduit |
| HTTP 401 from Conduit before any Acronis call |
A header is missing, or the data center URL is not https on acronis.com |
Reconnect with the data center URL Acronis showed for the API client |
| 403 from Acronis |
The tenant is outside the API client's tenant |
Use a tenant under the API client's tenant, or create the API client higher up |
| 404 from Acronis |
Wrong ID, or the wrong ID type (a resource ID where an agent ID belongs) |
Re-list from the parent and retry |
| 429 from Acronis |
Acronis is throttling the API client |
Wait and retry. Use count tools for fleet-wide sweeps. |
Conduit doesn't document a fixed Acronis rate limit for this connector. The
first call after a quiet period is slower because the connector signs in to
Acronis again.
Response Size
Each tool result is capped at about 100 KB. A larger result is cut off with a
truncation marker. When you see one, the data is incomplete: lower limit,
add filters, or page. Don't summarize a truncated result as if it were the
whole set.
Related Skills
1---2name: acronis-api-patterns3description: >4 Acronis Cyber Protect Cloud MCP fundamentals through Conduit: the three5 `X-Acronis-*` headers (data center URL, API client ID and secret), the6 partner → customer → unit tenant hierarchy and what an API client can see,7 the 37-tool surface (34 reads plus 3 writes that are off by default, one of8 them admin-only in Conduit), the `path` / `query` / `body` argument shape,9 the different pagination styles per API family, filter operator syntax,10 nanosecond alert timestamps, response size caps, and the error shape.11when_to_use: >-12 When connecting to Acronis through Conduit, building any Acronis tool call,13 paging through Acronis results, or diagnosing a failed Acronis call. Use14 when: acronis api, acronis authentication, acronis api client, acronis data15 center url, acronis pagination, acronis error, acronis mcp, acronis tools,16 or upstream_unavailable.17metadata:18 source: https://skillmd.com/skills/wyre-ai/acronis-api-patterns19---2021# Acronis MCP Tools & API Patterns2223## Overview2425Acronis Cyber Protect Cloud is a multi-tenant backup, disaster recovery and26endpoint protection platform. MSPs run it as a partner tenant with one27customer tenant per client. The Conduit connector wraps Acronis's own MCP28server and exposes a curated set of 37 tools. Tool names are `acronis_` plus29the Acronis operation name, such as `acronis_fetch_all_alerts`.3031## Connection & Authentication3233Conduit sends three headers to the Acronis connector:3435| Header | Conduit field | Value |36|--------|---------------|-------|37| `X-Acronis-Base-Url` | Data center URL | The data center Acronis shows when you create the API client, such as `https://us5-cloud.acronis.com`. Origin only: nothing after `.com`. |38| `X-Acronis-Client-Id` | Client ID | The API client's ID |39| `X-Acronis-Client-Secret` | Client Secret | The API client's secret |4041You enter these fields once in the Conduit web UI (`/connect/acronis`).42Conduit stores them and injects the headers on every request; nothing is set43on the client, and Conduit drops any `X-Acronis-*` header a client sends.4445How to get them:46471. In the Acronis management portal, open **Settings → API clients**.482. Create an API client. Copy the Client ID, the Secret and the data center49 URL that Acronis shows. The secret is only shown once.503. Don't use your Acronis portal email and password. Conduit needs an API51 client, which signs in with the OAuth `client_credentials` flow.5253When you connect, Conduit checks the data center URL (it must be `https` on an54`acronis.com` host) and does a real token exchange with Acronis, so a wrong55secret or the wrong data center fails at connect time, not on the first tool56call.5758### What the connection can see5960- Everyone in your Conduit org shares this one connection.61- The API client sees only the tenant that owns it and the tenants under it.62 An API client created in the partner tenant sees every customer. One created63 inside a customer tenant sees only that customer.6465## Tenant Hierarchy6667```68Partner (the MSP) → [Folder] → Customer (a client) → [Unit]69```7071Almost every read filters by a tenant UUID. The parameter name differs by API72family, which is the most common source of empty results:7374| API family | Tenant parameter |75|-----------|------------------|76| Account management (tenants, users, usage, MFA) | `tenant_id` in `path`, or `parent_id` / `subtree_root_id` / `uuids` in `query` |77| Alerts | `tenant` (an array) in `query`; per-customer tools use `customer_id` |78| Policies, resources, protection status | `tenant_id` in `query` |79| Agents | `tenant_id` in `query`, meaning a subtree root |80| EDR incidents | `customer_id` in `query` |8182## Tool Surface8384All tools are listed directly. There is no navigation step.8586| Area | Tools |87|------|-------|88| Tenants and users | `acronis_fetch_tenant`, `acronis_fetch_tenants_batch`, `acronis_fetch_tenant_children`, `acronis_fetch_tenant_users`, `acronis_fetch_users_batch`, `acronis_fetch_user`, `acronis_fetch_current_user_info`, `acronis_search`, `acronis_fetch_tenant_mfa_status`, `acronis_fetch_tenant_usages` |89| Alerts | `acronis_fetch_all_alerts`, `acronis_fetch_alert`, `acronis_fetch_categories`, `acronis_fetch_alert_counters`, `acronis_fetch_alerts_grouped_by_scope`, `acronis_fetch_all_alert_types`, `acronis_fetch_resources_with_top_severity_alerts`, `acronis_fetch_alert_counts_per_customer`, `acronis_fetch_alerts_grouped_per_customer`, `acronis_fetch_active_alert_count` |90| Protection policies (protection plans) | `acronis_fetch_policies`, `acronis_fetch_policy`, `acronis_fetch_policy_applications`, `acronis_fetch_applications_issue_statistics`, `acronis_fetch_application_statuses_by_policy` |91| Resources (machines, mailboxes, workloads) | `acronis_fetch_resources`, `acronis_fetch_resource_count`, `acronis_fetch_resource`, `acronis_fetch_resource_protection_status` |92| Agents | `acronis_fetch_agents`, `acronis_fetch_agent` |93| EDR incidents | `acronis_fetch_incidents`, `acronis_fetch_incident`, `acronis_fetch_response_action_status` |94| Writes (off by default) | `acronis_mark_alert_as_false_positive`, `acronis_update_investigation_state`, `acronis_execute_protection_policy` |9596### Writes and Conduit permission tiers9798The three write tools are **off by default**. They don't appear in the tool99list until WYRE turns writes on for the Acronis connector. When they are on,100Conduit gates them by permission tier:101102| Tool | Conduit tier | What it changes |103|------|--------------|-----------------|104| All 34 reads | read | Nothing |105| `acronis_mark_alert_as_false_positive` | write | Sets or clears the false-positive flag on an alert, for everyone in Acronis |106| `acronis_update_investigation_state` | write | Changes an EDR incident's investigation state or adds a comment |107| `acronis_execute_protection_policy` | **admin** | Runs a protection plan now on every machine it covers, starting backup or protection jobs |108109If a write tool is missing from the tool list, writes are off. Say so plainly110and give the operator the console path instead of looking for a workaround.111112### Not available through this connector113114Creating or deleting tenants, users or API clients, any delete, pricing and115offering items, registration tokens, branding, and starting EDR response116actions (such as isolating a machine) are not exposed at all. Reading the117status of a response action that was started in the console is available118through `acronis_fetch_response_action_status`.119120## Argument Shape121122Arguments are grouped the way the Acronis REST API groups them: `path` for123URL path parameters, `query` for query-string filters, and `body` for write124payloads. A few tools also take `headers`.125126```json127{128 "path": { "tenant_id": "0f8fad5b-d9cb-469f-a165-70867728950e" },129 "query": { "embed_path": true }130}131```132133Tenant, user and policy IDs are lowercase UUIDs. Several filters take a134comma-separated list of up to 100 UUIDs in one string, such as `uuids` on135`acronis_fetch_tenants_batch` and `tenant_id` on `acronis_fetch_resources`.136137## Pagination138139Each Acronis API family pages differently. Check for a next cursor before you140say a list is complete.141142| Tools | How to page |143|-------|-------------|144| `acronis_fetch_tenants_batch`, `acronis_fetch_users_batch`, `acronis_fetch_tenant_children` | `limit` plus `after`. Read the next cursor from `paging.cursors.after`. The cursor carries the filters, so pass only `after` on later pages. |145| `acronis_fetch_policies`, `acronis_fetch_policy_applications`, `acronis_fetch_application_statuses_by_policy`, `acronis_fetch_resources`, `acronis_fetch_resource_protection_status` | `limit` plus `after` / `before` cursors |146| `acronis_fetch_agents` | `limit` plus `after` / `before`. Leaving `limit` out or setting it to 0 returns every agent, which can hit the response size cap. |147| `acronis_fetch_incidents` | `limit` plus `cursor`. Every other filter and the sort order must stay exactly the same between pages. |148| `acronis_fetch_all_alerts` | No cursor. `limit` caps the result. Narrow with filters (`tenant`, `category`, `severity`, `created_at`) and use `skip` to leave out alert IDs you've already seen. |149150For counts, use the count tools instead of paging: `acronis_fetch_resource_count`,151`acronis_fetch_alert_counters`, `acronis_fetch_alert_counts_per_customer` and152`acronis_fetch_active_alert_count`.153154## Filter Syntax155156- **Alerts** use operator functions: `severity: "or(warning,critical)"`,157 `severity: "gt(warning)"`, `planName: ["eq(Daily backup)"]`. A bare158 `planName` or `resourceName` value matches a substring. IDs passed with159 `or(...)` match exactly.160- **Alert timestamps** (`created_at`, `updated_at`, `deleted_at`) are Unix161 time in **nanoseconds**, with an operator:162 `created_at: "gt(1793491200000000000)"` means after 2026-11-01 00:00 UTC.163 Seconds or milliseconds silently match nothing useful.164- **EDR incidents** use `range(date_from, date_to)` and `ge(date_from)` for165 `created_at` / `updated_at`, and `or(a,b)` for `state`, `severity` and166 `mitigation_state`.167- **Policies and resources** take a `search` string with an SQL-like syntax168 over name, type and tags.169170## Errors171172The connector returns errors as JSON:173174```json175{ "error": { "code": "upstream_unavailable", "message": "..." } }176```177178Messages are capped at 500 characters and never contain the client secret.179180| Symptom | Cause | What to do |181|---------|-------|-----------|182| `upstream_unavailable` | The connector could not start a session with Acronis: the API client was disabled or its secret rotated, or the data center can't be reached | Re-check the API client under Settings → API clients and reconnect Acronis in Conduit |183| HTTP 401 from Conduit before any Acronis call | A header is missing, or the data center URL is not `https` on `acronis.com` | Reconnect with the data center URL Acronis showed for the API client |184| 403 from Acronis | The tenant is outside the API client's tenant | Use a tenant under the API client's tenant, or create the API client higher up |185| 404 from Acronis | Wrong ID, or the wrong ID type (a resource ID where an agent ID belongs) | Re-list from the parent and retry |186| 429 from Acronis | Acronis is throttling the API client | Wait and retry. Use count tools for fleet-wide sweeps. |187188Conduit doesn't document a fixed Acronis rate limit for this connector. The189first call after a quiet period is slower because the connector signs in to190Acronis again.191192## Response Size193194Each tool result is capped at about 100 KB. A larger result is cut off with a195truncation marker. When you see one, the data is incomplete: lower `limit`,196add filters, or page. Don't summarize a truncated result as if it were the197whole set.198199## Related Skills200201- [backup-health](../backup-health/SKILL.md) - Alert-driven backup triage across customers202- [protection-coverage](../protection-coverage/SKILL.md) - Unprotected machines, plan issues and agent hygiene203- [edr-incidents](../edr-incidents/SKILL.md) - EDR incident review and investigation state204- [tenants-and-usage](../tenants-and-usage/SKILL.md) - Customer mapping, usage, users and MFA posture