capture_camera_set
Capture 1-8 saved camera bookmarks in exact order. Returns a labeled manifest followed by ordered inline PNGs. Every successful run transactionally becomes the previous session baseline within a 64-entry/64 MiB memory budget; comparePrevious reports SkiaSharp RGBA delta metrics. renderUI defaults...
This record as markdown: /tools/sbox/capture-camera-set.md
What capture_camera_set does on Sbox
AI agents use capture_camera_set to create or update resources in Sbox, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sbox environment.
Why capture_camera_set is rated Medium
An AI agent can call capture_camera_set faster than any human can review: one bad instruction and it creates or modifies resources in Sbox by the hundred, each call as confident as the last.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs capture_camera_set 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 capture_camera_set, this is the rule to start with:
capture_camera_set stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 capture_camera_set call is checked against it from then on.
Questions about capture_camera_set
Capture 1-8 saved camera bookmarks in exact order. Returns a labeled manifest followed by ordered inline PNGs. Every successful run transactionally becomes the previous session baseline within a 64-entry/64 MiB memory budget; comparePrevious reports SkiaSharp RGBA delta metrics. renderUI defaults false for stable comparisons. Physics-trace occlusion is diagnostic and never moves the camera. It is categorised as a Write tool in the Sbox MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sbox MCP server in PolicyLayer and add a rule for capture_camera_set: 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.
capture_camera_set is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the capture_camera_set 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 capture_camera_set. 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.
capture_camera_set 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