Remove guest OS mapping
AI agents call remove_guest_os_mapping to permanently remove resources in CloudStack MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool removes (deletes) a guest OS mapping, which is a configuration that maps guest operating systems to hypervisor types. This deletion cannot be undone and would break the ability to provision VMs with that OS type until the mapping is re-added. While not directly impacting running VMs, it is an irreversible infrastructure configuration change that affects system functionality.
From the tool's definition Tool name contains 'remove' which indicates deletion; description states 'Remove guest OS mapping' confirming irreversible deletion of a configuration mapping.
Attacks that exploit this kind of access
Remove guest OS mapping. It is categorised as a Destructive tool in the CloudStack MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for remove_guest_os_mapping: 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 CloudStack MCP Server. Nothing to install.
remove_guest_os_mapping 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_guest_os_mapping 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_guest_os_mapping. 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_guest_os_mapping is provided by the CloudStack MCP Server MCP server (mozg31337/cloudstack-mcp-server). 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 →