Add guest OS mapping
AI agents use add_guest_os_mapping to create or update resources in CloudStack MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CloudStack MCP Server environment.
This tool creates or modifies a guest OS mapping, which is a configuration entity mapping guest operating systems to CloudStack hypervisor configurations. This is reversible (mappings can be updated or removed later) and has moderate blast radius if misconfigured—it could cause VMs launched with that mapping to fail or behave incorrectly, but does not directly delete data or execute arbitrary code.
From the tool's definition Tool name 'add_guest_os_mapping' indicates a creation/addition operation. The description 'Add guest OS mapping' confirms this creates a new guest OS mapping configuration in the CloudStack infrastructure.
Attacks that exploit this kind of access
Add guest OS mapping. It is categorised as a Write tool in the CloudStack MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for add_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.
add_guest_os_mapping is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_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 add_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.
add_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 →