apply_post_fx_look
Apply just a camera post-processing look (no lights/fog): cinematic (tonemap + bloom + soft vignette), filmic-horror (desaturated, high-contrast, heavy vignette, film grain), or clean (tonemap only).
This record as markdown: /tools/sbox/apply-post-fx-look.md
What apply_post_fx_look does on Sbox
AI agents use apply_post_fx_look 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 apply_post_fx_look is rated Medium
This tool creates or modifies visual rendering state (post-processing effects) within the game engine. It is reversible—other post-processing looks can be applied or removed. It does not execute arbitrary code, delete data, or trigger external operations. The write category is appropriate for non-destructive creation/modification of game asset properties.
From the tool's definition Tool name 'apply_post_fx_look' and description state it 'Apply[s]' camera post-processing effects by setting visual parameters (tonemap, bloom, vignette, film grain, desaturation, contrast). These are non-destructive modifications to render settings.
Attacks that exploit this kind of access
The rule that runs apply_post_fx_look 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 apply_post_fx_look, this is the rule to start with:
apply_post_fx_look 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 apply_post_fx_look call is checked against it from then on.
Questions about apply_post_fx_look
Apply just a camera post-processing look (no lights/fog): cinematic (tonemap + bloom + soft vignette), filmic-horror (desaturated, high-contrast, heavy vignette, film grain), or clean (tonemap only). 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 apply_post_fx_look: 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.
apply_post_fx_look 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 apply_post_fx_look 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 apply_post_fx_look. 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.
apply_post_fx_look 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