run_background_task · Virtualbox MCP Server MCP

WHAT IT DOES

What run_background_task does on Virtualbox MCP Server

AI agents invoke run_background_task to trigger actions in Virtualbox 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 run_background_task needs a policy

This tool executes code/commands on a remote system (the VM) with effects determined by the command argument. The background execution and VM context make it high severity because an AI agent could run destructive, financial, or reconnaissance commands without user visibility. It does not irreversibly delete data (not Destructive), does not move money (not Financial), and is not merely reading data (not Read).

From the tool's definition Tool description states 'Run a command in the VM as a background task' — this directly executes arbitrary commands within a virtual machine environment.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_background_task Rate-limited

run_background_task 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": {
    "run_background_task": {
      "limits": [
        {
          "counter": "run_background_task_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 Virtualbox MCP Server, so you can run agents against it safely.

FAQ

Questions about run_background_task

What does the run_background_task tool do? +

Run a command in the VM as a background task. It is categorised as a Execute tool in the Virtualbox 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 run_background_task? +

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

What risk level is run_background_task? +

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

Can I rate-limit run_background_task? +

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

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

run_background_task is provided by the Virtualbox MCP Server MCP server (usemanusai/virtualbox-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.