environment_set_sky
Attach a Sky to an existing Environment resource file (setting a ProceduralSkyMaterial, PhysicalSkyMaterial, or PanoramaSkyMaterial) and switch its background to SKY, then re-save. DESTRUCTIVE (writes a file) — gated by confirmation. Refuses a path that is not an Environment.
This record as markdown: /tools/breakpoint-mcp/environment-set-sky.md
What environment_set_sky does on Breakpoint
AI agents use environment_set_sky to create or update resources in Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Breakpoint environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Environment res:// path |
confirm | boolean | — | Auto-approve this destructive action (skip the confirmation prompt) |
sky_material | string | — | Sky material kind (default procedural) |
Parameters from the server's own tool schema.
Why environment_set_sky is rated Medium
Despite the tool labeling itself 'DESTRUCTIVE', it writes/modifies an existing Environment resource file rather than deleting or irreversibly destroying data. It overwrites the file with new sky settings, which is a reversible modification (the file can be restored). The label 'DESTRUCTIVE' here refers to file-writing side effects, not irreversible deletion. It is gated by confirmation, reducing blast radius.
From the tool's definition Attach a Sky to an existing Environment resource file...and switch its background to SKY, then re-save. DESTRUCTIVE (writes a file) — gated by confirmation.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs environment_set_sky safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For environment_set_sky, this is the rule to start with:
environment_set_sky 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 Breakpoint, apply this rule, and every environment_set_sky call is checked against it from then on.
Questions about environment_set_sky
Attach a Sky to an existing Environment resource file (setting a ProceduralSkyMaterial, PhysicalSkyMaterial, or PanoramaSkyMaterial) and switch its background to SKY, then re-save. DESTRUCTIVE (writes a file) — gated by confirmation. Refuses a path that is not an Environment. It is categorised as a Write tool in the Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
environment_set_sky accepts 3 parameters: path, confirm, sky_material. Required: path. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for environment_set_sky: 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 Breakpoint. Nothing to install.
environment_set_sky 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 environment_set_sky 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 environment_set_sky. 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.
environment_set_sky is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
This server
Across the catalogue