device_authorization_approval
[Account Management API 2] Approves existing device code. In case of setting tenant_uuid parameter in the request body or in the scope the current user and target tenant should satisfy next requirements: user should be a partner_admin, user should have RW access to the target tenant, target tenan...
This record as markdown: /tools/acronis-platform-mcp/device-authorization-approval.md
What device_authorization_approval does on Acronis Platform
AI agents call device_authorization_approval 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 |
|---|---|---|---|
body | object | — | Request body (JSON object) |
Parameters from the server's own tool schema.
Why device_authorization_approval is rated Low
Even though device_authorization_approval 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 signalsAccepts freeform code/query input (body.code) · Accepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs device_authorization_approval 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 device_authorization_approval, this is the rule to start with:
device_authorization_approval 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 device_authorization_approval call is checked against it from then on.
Questions about device_authorization_approval
[Account Management API 2] Approves existing device code. In case of setting tenant_uuid parameter in the request body or in the scope the current user and target tenant should satisfy next requirements: user should be a partner_admin, user should have RW access to the target tenant, target tenant should be personal, target tenant's owner should have protection_admin or backup_user roles. It is categorised as a Read tool in the Acronis Platform MCP Server, which means it retrieves data without modifying state.
device_authorization_approval 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 device_authorization_approval: 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.
device_authorization_approval 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 device_authorization_approval 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 device_authorization_approval. 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.
device_authorization_approval 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