AI agents use set_white_balance_auto to create or update resources in So Dsc — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your So Dsc environment.
This tool modifies a camera setting (white balance mode) by changing it to automatic. It is a reversible configuration change with no destructive, financial, or code-execution implications. Blast radius is minimal — it only affects camera white balance behavior.
From the tool's definition Switch white balance to Auto WB
Attacks that exploit this kind of access
Switch white balance to Auto WB. It is categorised as a Write tool in the So Dsc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the So Dsc MCP server in PolicyLayer and add a rule for set_white_balance_auto: 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 So Dsc. Nothing to install.
set_white_balance_auto 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 set_white_balance_auto 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 set_white_balance_auto. 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.
set_white_balance_auto is provided by the So Dsc MCP server (nananek/so-dsc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →