Clone/duplicate a computer including its full disk state. Creates an identical copy. Use when spinning up parallel agents on the same starting environment, or snapshotting a known-good state before risky changes.
AI agents use orgo_clone_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.
This tool creates a new resource (duplicate computer with full disk state copy) which is a Write operation—it modifies the system state by adding a new computer. It is reversible (the clone can be deleted), so it does not meet the Destructive threshold.
From the tool's definition Tool description states 'Clone/duplicate a computer including its full disk state. Creates an identical copy.'
Documented attack patterns abuse exactly the kind of access orgo_clone_computer gives an agent:
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_clone_computer:
{
"version": "1",
"default": "deny",
"tools": {
"orgo_clone_computer": {
"limits": [
{
"counter": "orgo_clone_computer_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} orgo_clone_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.
Free to start. No card required.
Clone/duplicate a computer including its full disk state. Creates an identical copy. Use when spinning up parallel agents on the same starting environment, or snapshotting a known-good state before risky changes. 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.
Register the Orgo MCP Server MCP server in PolicyLayer and add a rule for orgo_clone_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.
orgo_clone_computer is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the orgo_clone_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.
Set action: deny in the PolicyLayer policy for orgo_clone_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.
orgo_clone_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.
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.
Free to start. No card required.
28 Orgo MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.