fibaro_set_device_value

Set a specific property value for a device. Use this ONLY for advanced properties like temperature setpoints, modes, or custom device properties. Do NOT use for brightness (use fibaro_set_brightness) or colors (use fibaro_set_color).

Server Fibaro HC3 MCP Server kaeljune/fibaro-mcp-server
Category Write
Risk class Medium
Parameters 00 required

What fibaro_set_device_value does on Fibaro HC3 MCP Server

AI agents use fibaro_set_device_value to create or update resources in Fibaro HC3 MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fibaro HC3 MCP Server environment.

Why fibaro_set_device_value needs a policy

This tool modifies device state/properties on smart home devices (temperature setpoints, modes, custom properties). It's a Write operation as it changes configuration/state of physical devices. It's reversible since values can be changed back. Severity is medium because misconfiguration of smart home devices (e.g., temperature setpoints) could have real-world physical effects but is generally recoverable.

From the tool's definition Set a specific property value for a device... advanced properties like temperature setpoints, modes, or custom device properties

Questions about fibaro_set_device_value

What does the fibaro_set_device_value tool do? +

Set a specific property value for a device. Use this ONLY for advanced properties like temperature setpoints, modes, or custom device properties. Do NOT use for brightness (use fibaro_set_brightness) or colors (use fibaro_set_color). It is categorised as a Write tool in the Fibaro HC3 MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on fibaro_set_device_value? +

Register the Fibaro HC3 MCP Server MCP server in PolicyLayer and add a rule for fibaro_set_device_value: 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_set_device_value? +

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

Can I rate-limit fibaro_set_device_value? +

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

Set action: deny in the PolicyLayer policy for fibaro_set_device_value. 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_set_device_value? +

fibaro_set_device_value 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.