remove_a_policy_from_a_draft
[Resource and Policy Management API v4] Removes the specified policy from the draft composite; linked downstream policies may be affected, so the full draft is returned.
This record as markdown: /tools/acronis-platform-mcp/remove-a-policy-from-a-draft.md
What remove_a_policy_from_a_draft does on Acronis Platform
AI agents call remove_a_policy_from_a_draft to permanently remove resources in Acronis Platform, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | object | Yes | URI path parameters |
Parameters from the server's own tool schema.
Why remove_a_policy_from_a_draft is rated Critical
An AI agent that decides to call remove_a_policy_from_a_draft doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Acronis Platform is gone. There is no undo for destructive operations.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs remove_a_policy_from_a_draft 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 remove_a_policy_from_a_draft, this is the rule to start with:
remove_a_policy_from_a_draft is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Acronis Platform, apply this rule, and every remove_a_policy_from_a_draft call is checked against it from then on.
Questions about remove_a_policy_from_a_draft
[Resource and Policy Management API v4] Removes the specified policy from the draft composite; linked downstream policies may be affected, so the full draft is returned. It is categorised as a Destructive tool in the Acronis Platform MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
remove_a_policy_from_a_draft accepts 1 parameter: path. Required: path. 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 remove_a_policy_from_a_draft: 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.
remove_a_policy_from_a_draft is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_a_policy_from_a_draft 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 remove_a_policy_from_a_draft. 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.
remove_a_policy_from_a_draft 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.
Across the catalogue