AI agents invoke power_off_vm to trigger actions in Nutanix. 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.
Powering off a VM triggers an external operation (graceful shutdown) on a running virtual machine. This is an Execute-category action because it causes a significant state change on infrastructure. While it is not fully irreversible (the VM can be powered back on with power_on_vm), it disrupts running workloads and services, warranting a high severity rating due to potential service outages if misused by an AI agent.
From the tool's definition Transition a VM from On to Off (graceful shutdown)
Attacks that exploit this kind of access
Transition a VM from On to Off (graceful shutdown). It is categorised as a Execute tool in the Nutanix MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nutanix MCP server in PolicyLayer and add a rule for power_off_vm: 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 Nutanix. Nothing to install.
power_off_vm 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 power_off_vm 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 power_off_vm. 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.
power_off_vm is provided by the Nutanix MCP server (nobanks/nutanix-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 →