fibaro_run_scene · Fibaro HC3 MCP Server MCP: Risk & Policy

WHAT IT DOES

What fibaro_run_scene does on Fibaro HC3 MCP Server

AI agents invoke fibaro_run_scene to trigger actions in Fibaro HC3 MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why fibaro_run_scene needs a policy

This tool executes a scene in the Fibaro HC3 smart home system. While scenes are predefined and not arbitrary code, they represent external operations whose effects depend on which scene is invoked—a user or agent could trigger scenes that lock/unlock doors, disarm alarms, disable security cameras, or perform other significant home automation actions.

From the tool's definition The tool description states 'Run/start a scene', which triggers execution of predefined automation sequences in a smart home system. Scenes can control multiple devices simultaneously and perform complex actions.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

fibaro_run_scene Rate-limited

fibaro_run_scene stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "fibaro_run_scene": {
      "limits": [
        {
          "counter": "fibaro_run_scene_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Fibaro HC3 MCP Server, so you can run agents against it safely.

FAQ

Questions about fibaro_run_scene

What does the fibaro_run_scene tool do? +

Run/start a scene. It is categorised as a Execute tool in the Fibaro HC3 MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on fibaro_run_scene? +

Register the Fibaro HC3 MCP Server MCP server in PolicyLayer and add a rule for fibaro_run_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 Fibaro HC3 MCP Server. Nothing to install.

What risk level is fibaro_run_scene? +

fibaro_run_scene is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit fibaro_run_scene? +

Yes. Add a rate_limit block to the fibaro_run_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 fibaro_run_scene completely? +

Set action: deny in the PolicyLayer policy for fibaro_run_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 fibaro_run_scene? +

fibaro_run_scene is provided by the Fibaro HC3 MCP Server MCP server (kaeljune/fibaro-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.