update_scene
AI agents use update_scene to create or update resources in SmartThingsMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SmartThingsMCP environment.
The tool modifies existing SmartThings scenes (update implies in-place changes), which is a Write operation. It is not Destructive because 'update' typically preserves the scene entity itself and prior state can be recovered. It is not Read as it produces side effects.
From the tool's definition Tool name 'update_scene' indicates modification of scene objects; no description provided, but naming convention and context (SmartThings automation/scene management) suggests reversible state changes.
Attacks that exploit this kind of access
update_scene. It is categorised as a Write tool in the SmartThingsMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SmartThings MCP server in PolicyLayer and add a rule for update_scene: 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 SmartThingsMCP. Nothing to install.
update_scene 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 update_scene 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 update_scene. 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.
update_scene is provided by the SmartThings MCP server (technohead/smartthings-mcp). 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 →