provision_vm_with_script
AI agents invoke provision_vm_with_script to trigger actions in Morpheus 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.
Provisioning a VM with a script combines resource creation with arbitrary code execution. The script component elevates this beyond a simple Write operation to Execute, as scripts can have wide-ranging effects on infrastructure. The blast radius is critical because misuse could spin up expensive cloud resources and execute malicious code in a multi-tenant environment.
From the tool's definition Tool name 'provision_vm_with_script' implies both provisioning a VM (Write/Execute) and executing a script during provisioning. The server description mentions 'provision resources' and 'execute workflows'.
Attacks that exploit this kind of access
provision_vm_with_script. It is categorised as a Execute tool in the Morpheus MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Morpheus MCP Server MCP server in PolicyLayer and add a rule for provision_vm_with_script: 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 Morpheus MCP Server. Nothing to install.
provision_vm_with_script 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 provision_vm_with_script 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 provision_vm_with_script. 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.
provision_vm_with_script is provided by the Morpheus MCP Server MCP server (nixndme/morpheus-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 →