Sceneplane

Update deployment policy

deployment_policy_update

Destructive

Change execution limits, approvals or scripting for an existing deployment; omitted fields remain unchanged. Requires owner/admin and deployments:admin scope for narrowed credentials; only the owner may toggle dangerousScriptingEnabled. May restrict future work or enable arbitrary Blender Python. Validates platform and plan ceilings, records a policy version, and rejects concurrent policy edits. Use deployment_update to rename or enable/disable the workspace, or deployments_list to find its slug. Returns policyVersion and scriptingEnabled.

Input Schema

TableJSON Schema

Name	Required	Description
`deployment`	Yes	deployment slug
`maxQueuedJobs`	No	Maximum queued jobs for this deployment, 1-200, subject to the account plan; a full queue rejects new submissions.
`renderMaxWidth`	No	Maximum render width in pixels, 16-4096, additionally capped by the account plan.
`renderMaxHeight`	No	Maximum render height in pixels, 16-4096, additionally capped by the account plan.
`renderMaxSamples`	No	Maximum render samples, 1-4096, additionally capped by the account plan.
`jobTimeoutSeconds`	No	Execution timeout per job in seconds, 10-3600, additionally bounded by the account plan.
`maxConcurrentJobs`	No	Concurrent worker/job limit for this deployment, 1-20, subject to the account plan. Raising this does not bypass shared account quotas.
`renderApprovalThreshold`	No	widthheightsamples above which renders need interactive approval; capped at the plan's renderMaxWidthrenderMaxHeightrenderMaxSamples
`maxOperationsPerMutation`	No	Maximum scene_apply operations per batch, 1-128. Omit to preserve the current batch limit.
`dangerousScriptingEnabled`	No	Owner-only switch for scene_script arbitrary Blender Python. True enables scripting; false disables it. Omit to leave the existing security policy unchanged.
`approvalRequiredForRestore`	No	Whether revision_restore must obtain interactive approval before replacing the current scene head. Omit to preserve the existing setting.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	Yes
`policyVersion`	Yes
`scriptingEnabled`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedSep 30, 2026

addedInput schema / properties / approvalRequiredForRestore / description

Added value: +"Whether revision_restore must obtain interactive approval before replacing the current scene head. Omit to preserve the existing setting."

addedInput schema / properties / dangerousScriptingEnabled / description

Added value: +"Owner-only switch for scene_script arbitrary Blender Python. True enables scripting; false disables it. Omit to leave the existing security policy unchanged."

addedInput schema / properties / jobTimeoutSeconds / description

Added value: +"Execution timeout per job in seconds, 10-3600, additionally bounded by the account plan."

addedInput schema / properties / maxConcurrentJobs / description

Added value: +"Concurrent worker/job limit for this deployment, 1-20, subject to the account plan. Raising this does not bypass shared account quotas."

addedInput schema / properties / maxOperationsPerMutation / description

Added value: +"Maximum scene_apply operations per batch, 1-128. Omit to preserve the current batch limit."

addedInput schema / properties / maxQueuedJobs / description

Added value: +"Maximum queued jobs for this deployment, 1-200, subject to the account plan; a full queue rejects new submissions."

addedInput schema / properties / renderMaxHeight / description

Added value: +"Maximum render height in pixels, 16-4096, additionally capped by the account plan."

addedInput schema / properties / renderMaxSamples / description

Added value: +"Maximum render samples, 1-4096, additionally capped by the account plan."

addedInput schema / properties / renderMaxWidth / description

Added value: +"Maximum render width in pixels, 16-4096, additionally capped by the account plan."

First observedSep 24, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations (destructiveHint=true, idempotentHint=false) by disclosing partial-update semantics ('omitted fields remain unchanged'), the owner-only restriction on dangerousScriptingEnabled, plan/platform ceiling validation, policy version recording, and rejection of concurrent edits. This is exactly the behavioral context the annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and the omitted-fields rule, then routing guidance. Dense with no filler, but it packs many clauses into a single long paragraph, which slightly hurts scannability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive 11-param mutation with an output schema, the description covers auth requirements, partial-update behavior, concurrency, validation, and even the return fields (policyVersion, scriptingEnabled). Nothing material is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all 11 parameters and the baseline is 3. The description still adds meaning not in the schema: omitted fields preserve current values, and only the owner may flip dangerousScriptingEnabled. That extra semantic is useful but limited in scope, so a 4 rather than a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a precise verb+resource ('Change execution limits, approvals or scripting for an existing deployment') and explicitly carves out scope against siblings like deployment_update and deployments_list. An agent can distinguish it from the other deployment_* tools without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the alternatives and the conditions that route elsewhere: 'Use deployment_update to rename or enable/disable the workspace, or deployments_list to find its slug.' Also gives the prerequisite auth (owner/admin and deployments:admin). Explicit when-to-use and when-not.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Sceneplane tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?