New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

manage_scene

Named scene management. action: capture (save current item states), activate (restore a saved scene).

SERVEROpenhab SOURCEdeswong/openhab-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/deswong-openhab-mcp/manage-scene.md

What manage_scene does on Openhab

AI agents use manage_scene to create or update resources in Openhab, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Openhab environment.

Why manage_scene is rated Medium

The capture action saves/creates scene data (Write), and activate modifies the live state of items in the home (Write). While these are reversible (scenes can be overwritten or different scenes activated), they directly alter the operational state of controlled devices. The high severity reflects that misuse could change HVAC settings, locks, lighting, or other critical home systems.

From the tool's definition Tool performs 'capture (save current item states)' and 'activate (restore a saved scene)' — both are state modification operations that persist changes to the home automation system.

Questions about manage_scene

What does the manage_scene tool do? +

Named scene management. action: capture (save current item states), activate (restore a saved scene). It is categorised as a Write tool in the Openhab MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on manage_scene? +

Register the Openhab MCP server in PolicyLayer and add a rule for manage_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 Openhab. Nothing to install.

What risk level is manage_scene? +

manage_scene is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit manage_scene? +

Yes. Add a rate_limit block to the manage_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.

How do I block manage_scene completely? +

Set action: deny in the PolicyLayer policy for manage_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.

What MCP server provides manage_scene? +

manage_scene is provided by the Openhab MCP server (deswong/openhab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Openhab, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Openhab's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.