New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

remove_guest_os_mapping

A destructive tool on the CloudStack MCP server.

SERVERCloudStack MCP Server SOURCEmozg31337/cloudstack-mcp-server
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mozg31337-cloudstack-mcp-server/remove-guest-os-mapping.md

What remove_guest_os_mapping does on CloudStack MCP Server

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.

Why remove_guest_os_mapping is rated Critical

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.

Questions about remove_guest_os_mapping

What does the remove_guest_os_mapping tool do? +

remove_guest_os_mapping is a destructive tool on the CloudStack MCP Server MCP server. 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.

How do I enforce a policy on remove_guest_os_mapping? +

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.

What risk level is remove_guest_os_mapping? +

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.

Can I rate-limit remove_guest_os_mapping? +

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.

How do I block remove_guest_os_mapping completely? +

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.

What MCP server provides remove_guest_os_mapping? +

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.

More on CloudStack MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of CloudStack MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.