update_tenants_usages
[Account Management API 2] Updates the values of the usages specified in usage_type or associated with the offering items specified in offering_item. Depending on the combination of provided fields, the usage may be reported either per tenant or per resource. See the descriptions of the fields fo...
This record as markdown: /tools/acronis-platform-mcp/update-tenants-usages.md
What update_tenants_usages does on Acronis Platform
AI agents use update_tenants_usages 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) |
Parameters from the server's own tool schema.
Why update_tenants_usages is rated Medium
An AI agent can call update_tenants_usages 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) · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs update_tenants_usages 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 update_tenants_usages, this is the rule to start with:
update_tenants_usages 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 update_tenants_usages call is checked against it from then on.
Questions about update_tenants_usages
[Account Management API 2] Updates the values of the usages specified in usage_type or associated with the offering items specified in offering_item. Depending on the combination of provided fields, the usage may be reported either per tenant or per resource. See the descriptions of the fields for more details. Trustee is restricted either to be registered within root tenant kind or to have configured CyberApp (origin_id) with fully provisioned auth-consents through Application Manager Account server…. 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.
update_tenants_usages accepts 1 parameter: body. 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 update_tenants_usages: 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.
update_tenants_usages 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 update_tenants_usages 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 update_tenants_usages. 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.
update_tenants_usages 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