Operations for managing system disks
AI agents call sm_disk_operations to permanently remove resources in Systems Manager — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Disk management operations represent some of the highest-risk actions on a system. Formatting, repartitioning, or wiping disks can result in complete, irreversible data loss. Even operations like unmounting can disrupt running services. Given the server context of 'system updates, application installations, and remote host orchestration,' disk operations could affect entire remote hosts.
From the tool's definition 'Operations for managing system disks' - disk management operations can include formatting, partitioning, wiping, or unmounting disks, which are irreversible and destructive
Attacks that exploit this kind of access
Operations for managing system disks. It is categorised as a Destructive tool in the Systems Manager MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Systems Manager MCP server in PolicyLayer and add a rule for sm_disk_operations: 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 Systems Manager. Nothing to install.
sm_disk_operations 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 sm_disk_operations 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 sm_disk_operations. 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.
sm_disk_operations is provided by the Systems Manager MCP server (knuckles-team/systems-manager). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →