console_run

Run an s&box console command / ConCmd via Sandbox.ConsoleSystem.Run — e.g. a cvar (

SERVERSbox SOURCEsbox-mcp-server

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sbox/console-run.md

WHAT IT DOES

What console_run does on Sbox

AI agents invoke console_run to trigger actions in Sbox. 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.

RISK

Why console_run is rated High

This tool executes console commands in the s&box game engine runtime. Console systems typically provide access to powerful scripting, state manipulation, and potentially unsafe operations.

From the tool's definition Tool name includes 'run' and description explicitly states 'Run an s&box console command / ConCmd via Sandbox.ConsoleSystem.Run'.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs console_run safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sbox, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For console_run, this is the rule to start with:

console_run Rate-limited

console_run 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": {
    "console_run": {
      "limits": [
        {
          "counter": "console_run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sbox, apply this rule, and every console_run call is checked against it from then on.

FAQ

Questions about console_run

What does the console_run tool do? +

Run an s&box console command / ConCmd via Sandbox.ConsoleSystem.Run — e.g. a cvar (. It is categorised as a Execute tool in the Sbox MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on console_run? +

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

What risk level is console_run? +

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

Can I rate-limit console_run? +

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

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

console_run is provided by the Sbox MCP server (sbox-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sbox, and thousands of servers like it.

This server

All 207 Sbox tools → High-risk tools on this server →

Across the catalogue

shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →