drive_player_status
EXPERIMENTAL — Read the result of the most recently FINISHED drive_player job: which controller members were actually written (EyeAngles / WishVelocity / AnalogMove…), how many frames applied, and why it ended. Because drive_player runs across frames and returns immediately, this is how you confi...
This record as markdown: /tools/sbox/drive-player-status.md
What drive_player_status does on Sbox
AI agents call drive_player_status to retrieve information from Sbox without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why drive_player_status is rated Low
This tool only reads and reports the outcome of a previously executed drive_player job. It performs no modifications, deletions, or new operations—it simply retrieves status information for diagnostic and confirmation purposes. The EXPERIMENTAL designation does not elevate the risk category, as the function remains fundamentally a read operation with no destructive or side-effect-producing capabilities.
From the tool's definition Tool description explicitly states 'Read the result' and describes retrieving status information about a completed job: 'which controller members were actually written', 'how many frames applied', and 'why it ended'.
Attacks that exploit this kind of access
The rule that runs drive_player_status 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 drive_player_status, this is the rule to start with:
drive_player_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sbox, apply this rule, and every drive_player_status call is checked against it from then on.
Questions about drive_player_status
EXPERIMENTAL — Read the result of the most recently FINISHED drive_player job: which controller members were actually written (EyeAngles / WishVelocity / AnalogMove…), how many frames applied, and why it ended. Because drive_player runs across frames and returns immediately, this is how you confirm it took effect. Returns lastResult=null if no job has finished yet. It is categorised as a Read tool in the Sbox MCP Server, which means it retrieves data without modifying state.
Register the Sbox MCP server in PolicyLayer and add a rule for drive_player_status: 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.
drive_player_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the drive_player_status 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 drive_player_status. 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.
drive_player_status 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.
More on Sbox, and thousands of servers like it.
This server
Across the catalogue