orgo_move_computer

Move a computer to a different workspace. The computer keeps its ID and disk state. Use to reorganize fleets without recreating VMs; faster than clone + delete for live machines.

ServerOrgo MCP Server
CategoryWrite

How to control orgo_move_computer ↓

WHAT IT DOES

What orgo_move_computer does on Orgo MCP Server

AI agents use orgo_move_computer to create or update resources in Orgo MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Orgo MCP Server environment.

THE RISK

Medium Risk

Why orgo_move_computer needs a policy

This tool changes metadata about a computer resource (its workspace assignment) but does not execute code, delete infrastructure, move financial resources, or permanently destroy data. The operation is reversible—the computer can be moved to another workspace again.

From the tool's definition The tool description states it will "Move a computer to a different workspace" and mentions reorganizing fleets without recreating VMs. This modifies the organizational state of infrastructure (workspace membership) reversibly.

Documented attack patterns abuse exactly the kind of access orgo_move_computer gives an agent:

POLICY

How to control orgo_move_computer

PolicyLayer is an MCP gateway — it sits between your AI agents and Orgo MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for orgo_move_computer:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "orgo_move_computer": {
      "limits": [
        {
          "counter": "orgo_move_computer_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

orgo_move_computer stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register Orgo MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Orgo MCP Server tools

Destructive orgo_delete_computer Permanently delete a computer and all its data. Cannot be undone. Use only when explicitly Destructive orgo_delete_workspace Permanently delete a workspace and all of its computers. Cannot be undone. Use only when e Destructive orgo_restart_computer Restart a computer. Useful for recovering from unresponsive states. Use when commands hang Execute orgo_bash Execute a bash command on the VM. Uses WebSocket terminal (preferred) with REST API fallba Execute orgo_ensure_running Ensure a computer is running. Resumes suspended VMs automatically. Idempotent. Use before Execute orgo_exec Execute Python code on the computer. Returns output or error details. Use for computation, Execute orgo_wait Pause execution on the VM for a fixed duration. Useful for sequencing actions between scre Execute orgo_click Click at pixel (x, y) coordinates on the VM display. Coordinates are in 1280x720 model spa

All 28 Orgo MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about orgo_move_computer

What does the orgo_move_computer tool do? +

Move a computer to a different workspace. The computer keeps its ID and disk state. Use to reorganize fleets without recreating VMs; faster than clone + delete for live machines. It is categorised as a Write tool in the Orgo MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on orgo_move_computer? +

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

What risk level is orgo_move_computer? +

orgo_move_computer is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit orgo_move_computer? +

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

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

orgo_move_computer is provided by the Orgo MCP Server MCP server (nickvasilescu/orgo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Orgo MCP Server tool call.

Start from Orgo MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

28 Orgo MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.