frame_camera
Aim the s&box EDITOR viewport camera at a GameObject (by id) or a world point (position + optional radius), then call take_screenshot to capture that view. This is how Claude points its own screenshots at what it
This record as markdown: /tools/sbox/frame-camera.md
What frame_camera does on Sbox
AI agents invoke frame_camera 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.
Why frame_camera is rated High
The tool actively changes the state of the s&box editor environment (repositioning/aiming the viewport camera), which is an external operation with side effects beyond mere data retrieval. While it doesn't delete or modify game data, it triggers an action in an external application (the editor). It is preparatory to taking a screenshot, but the camera manipulation itself constitutes an Execute-level action.
From the tool's definition 'Aim the s&box EDITOR viewport camera at a GameObject (by id) or a world point (position + optional radius)' — this triggers an external operation in the s&box editor, manipulating the viewport camera state
Attacks that exploit this kind of access
The rule that runs frame_camera 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 frame_camera, this is the rule to start with:
frame_camera 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Sbox, apply this rule, and every frame_camera call is checked against it from then on.
Questions about frame_camera
Aim the s&box EDITOR viewport camera at a GameObject (by id) or a world point (position + optional radius), then call take_screenshot to capture that view. This is how Claude points its own screenshots at what it. 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.
Register the Sbox MCP server in PolicyLayer and add a rule for frame_camera: 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.
frame_camera 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 frame_camera 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 frame_camera. 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.
frame_camera 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