post_idp_device_authorization
[Account Management API 2] Registers device codes and issues device and user codes.
This record as markdown: /tools/acronis-platform-mcp/post-idp-device-authorization.md
What post_idp_device_authorization does on Acronis Platform
AI agents use post_idp_device_authorization 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 | string | — | Request body (application/x-www-form-urlencoded) |
Parameters from the server's own tool schema.
Why post_idp_device_authorization is rated Medium
An AI agent can call post_idp_device_authorization 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)
Attacks that exploit this kind of access
The rule that runs post_idp_device_authorization 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 post_idp_device_authorization, this is the rule to start with:
post_idp_device_authorization 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 post_idp_device_authorization call is checked against it from then on.
Questions about post_idp_device_authorization
[Account Management API 2] Registers device codes and issues device and user codes. 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.
post_idp_device_authorization 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 post_idp_device_authorization: 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.
post_idp_device_authorization 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 post_idp_device_authorization 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 post_idp_device_authorization. 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.
post_idp_device_authorization 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