Mount an ISO from the org library as virtual media on a device. Destructive —
AI agents invoke mount_iso to trigger actions in KVMFleet MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Mounting an ISO as virtual media on a device triggers an external operation that changes the device's state (attaching virtual media). While the description hints at 'Destructive', mounting an ISO is not inherently irreversible — it can typically be unmounted — making Execute the more accurate category. However, it does modify device configuration and could lead to unintended boots or data exposure.
From the tool's definition Mount an ISO from the org library as virtual media on a device. Destructive —
Attacks that exploit this kind of access
Mount an ISO from the org library as virtual media on a device. Destructive —. It is categorised as a Execute tool in the KVMFleet MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the KVMFleet MCP Server MCP server in PolicyLayer and add a rule for mount_iso: 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 KVMFleet MCP Server. Nothing to install.
mount_iso is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the mount_iso 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 mount_iso. 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.
mount_iso is provided by the KVMFleet MCP Server MCP server (kvmfleet/mcp). 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 →