simulate_input

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/simulate-input.md

WHAT IT DOES

What simulate_input does on Sbox

AI agents invoke simulate_input 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 simulate_input is rated High

Triggers in-game input actions programmatically, executing game behavior without human interaction.

From the tool's definition Press or release a named input action during PLAY mode

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs simulate_input 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 simulate_input, this is the rule to start with:

simulate_input Rate-limited

simulate_input 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": {
    "simulate_input": {
      "limits": [
        {
          "counter": "simulate_input_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 simulate_input call is checked against it from then on.

FAQ

Questions about simulate_input

What does the simulate_input tool do? +

Press or release a named input action during PLAY mode (via Sandbox.Input.SetAction) so input-driven behavior — jump, attack1, use, reload, IPressable, weapon fire — can be verified without a human at the keyboard. REQUIRES play mode and a named. 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 simulate_input? +

Register the Sbox MCP server in PolicyLayer and add a rule for simulate_input: 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 simulate_input? +

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

Can I rate-limit simulate_input? +

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

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

simulate_input 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 287 Sbox tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

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