Execute a bash command on the VM. Uses WebSocket terminal (preferred) with REST API fallback. Returns output plus the exit code when non-zero. Prefer this over GUI clicks for anything scriptable — file ops, installs, git, curl, process management — and over
AI agents invoke orgo_bash to trigger actions in Orgo 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.
This tool allows execution of arbitrary bash commands on a virtual machine, which is a classic Execute category operation. The critical severity reflects that bash command execution has nearly unlimited potential for harm depending on the command: it can read/write/delete files, install malware, modify system configuration, exfiltrate data, or launch further attacks.
From the tool's definition Tool name 'orgo_bash' and description 'Execute a bash command on the VM' explicitly indicate execution of arbitrary shell commands.
Documented attack patterns abuse exactly the kind of access orgo_bash 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_bash:
{
"version": "1",
"default": "deny",
"tools": {
"orgo_bash": {
"limits": [
{
"counter": "orgo_bash_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}orgo_bash 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.
Free to start. No card required.
Execute a bash command on the VM. Uses WebSocket terminal (preferred) with REST API fallback. Returns output plus the exit code when non-zero. Prefer this over GUI clicks for anything scriptable — file ops, installs, git, curl, process management — and over. It is categorised as a Execute tool in the Orgo MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Orgo MCP Server MCP server in PolicyLayer and add a rule for orgo_bash: 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_bash 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 orgo_bash 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_bash. 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_bash 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.