mold_startVirtualMachine · ABLESTACK MOLD MCP Server MCP

WHAT IT DOES

What mold_startVirtualMachine does on ABLESTACK MOLD MCP Server

AI agents invoke mold_startVirtualMachine to trigger actions in ABLESTACK MOLD 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.

WHY IT NEEDS A POLICY

Why mold_startVirtualMachine needs a policy

Starting a virtual machine is an Execute action—it runs a command/operation on cloud infrastructure with real-world effects (VM state change). While not destructive (the VM still exists afterward), it is a significant infrastructure operation that changes system state and consumes resources. The async job handling indicates backend operations are triggered.

From the tool's definition Tool name is 'mold_startVirtualMachine' and description indicates it 'startVirtualMachine(4.21)' with potential async job return. This directly triggers VM startup operations via CloudStack API.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mold_startVirtualMachine Rate-limited

mold_startVirtualMachine stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mold_startVirtualMachine": {
      "limits": [
        {
          "counter": "mold_startvirtualmachine_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ABLESTACK MOLD MCP Server, so you can run agents against it safely.

FAQ

Questions about mold_startVirtualMachine

What does the mold_startVirtualMachine tool do? +

startVirtualMachine(4.21). 반환에 jobid가 포함될 수 있음(비동기). It is categorised as a Execute tool in the ABLESTACK MOLD MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on mold_startVirtualMachine? +

Register the ABLESTACK MOLD MCP Server MCP server in PolicyLayer and add a rule for mold_startVirtualMachine: 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 ABLESTACK MOLD MCP Server. Nothing to install.

What risk level is mold_startVirtualMachine? +

mold_startVirtualMachine is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit mold_startVirtualMachine? +

Yes. Add a rate_limit block to the mold_startVirtualMachine 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 mold_startVirtualMachine completely? +

Set action: deny in the PolicyLayer policy for mold_startVirtualMachine. 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 mold_startVirtualMachine? +

mold_startVirtualMachine is provided by the ABLESTACK MOLD MCP Server MCP server (ycyun/ablestack-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.