HC3 MCP Server

81 tools. 32 can modify or destroy data without limits.

3 destructive tools with no built-in limits. Policy required.

Last updated:

32 can modify or destroy data
49 read-only
81 tools total

Community server · catalogue entry verified 29/06/2026

How to control HC3 MCP Server ↓

What HC3 MCP Server exposes to your agents

Read (49) Write / Execute (29) Destructive / Financial (3)
Critical Risk

The most dangerous HC3 MCP Server tools

32 of HC3 MCP Server's 81 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control HC3 MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and HC3 MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations
{
  "clear_all_notifications": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "create_backup": {
    "limits": [
      {
        "counter": "create_backup_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "arm_alarm_partition": {
    "limits": [
      {
        "counter": "arm_alarm_partition_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register HC3 MCP Server — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON HC3 →

Instant setup, no code required.

All 81 HC3 MCP Server tools

READ 49 tools
Read arm_alarm_partition Arm alarm partition Read can_create_backup Check if backups can be created Read explain_device_capabilities Get human-readable explanations of what devices can do and how to control them effectively Read get_alarm_devices Get alarm system devices Read get_alarm_history Get alarm system history Read get_alarm_partition Get specific alarm partition by ID Read get_alarm_partitions Get all alarm partitions Read get_automation_suggestions Get intelligent automation suggestions based on device usage patterns, time of day, and system state Read get_backups Get list of available backups Read get_climate_zone Get specific climate zone by ID Read get_climate_zones Get all climate zones Read get_custom_events Get all custom events Read get_debug_messages Get system debug messages Read get_device_info Get detailed information about a specific device including properties, capabilities, and current state Read get_device_relationships Get relationships between devices, including grouped devices, dependencies, and automation connections Read get_device_usage_patterns Get device usage patterns and statistics to help understand home automation behavior Read get_devices Get all devices from Fibaro HC3, with optional filtering by room or device type Read get_diagnostics Get system diagnostic information Read get_energy_data Get energy consumption data for devices or the entire system Read get_global_variables Get all global variables from the HC3 system Read get_hc3_configuration_guide Get comprehensive HC3 configuration documentation including network settings, users, rooms, Z-Wave setup, etc. Read get_hc3_lua_scenes_guide Get HC3 Lua Scenes programming documentation including conditions, triggers, actions, and examples Read get_hc3_programming_examples Get practical HC3 programming examples and code snippets for common automation scenarios Read get_hc3_quickapp_programming_guide Get HC3 Quick Apps programming documentation including Lua syntax, methods, HTTP/TCP/UDP clients, etc. Read get_home_status Get current home/away status and location information Read get_installed_plugins Get list of installed plugins on the system. Read get_ios_devices Get registered iOS devices Read get_ip_cameras Get list of available IP camera types for plugin installation. Read get_local_backup_status Get local backup status Read get_location_info Get location and geofencing information Read get_network_status Get network configuration and status information Read get_notifications Get system notifications Read get_plugin_types Get information about all plugin types available in the system with categories. Read get_plugin_view Get plugin view/configuration interface for a specific plugin or device. Read get_plugins Get all available plugins including installed and available plugins. Read get_quickapp Get specific QuickApp by ID Read get_quickapp_file Get detailed information about a specific QuickApp file including its content. Read get_quickapp_logs Get QuickApp logs Read get_quickapps Get all QuickApps Read get_remote_backup_status Get remote backup status Read get_rooms Get all rooms in the Fibaro HC3 system Read get_scenes Get all scenes from Fibaro HC3, with optional filtering by room Read get_sprinkler_system Get specific sprinkler system by ID Read get_sprinkler_systems Get all sprinkler systems Read get_system_context Get comprehensive system context including device capabilities, room layouts, scene purposes, and system intel Read get_system_info Get Fibaro HC3 system information including version, serial number, and status Read get_users Get all users configured in the HC3 system Read get_weather Get current weather information and forecast Read list_quickapp_files Get list of all source files for a QuickApp. Returns file names, types, and metadata without file content.

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about HC3 MCP Server

Can an AI agent delete data through the HC3 MCP Server MCP server? +

Yes. The HC3 MCP Server server exposes 3 destructive tools including clear_all_notifications, delete_plugin, delete_quickapp_file. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through HC3 MCP Server? +

The HC3 MCP Server server has 18 write tools including create_backup, create_child_device, create_custom_event. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach HC3 MCP Server.

How many tools does the HC3 MCP Server MCP server expose? +

81 tools across 4 categories: Destructive, Execute, Read, Write. 49 are read-only. 32 can modify, create, or delete data.

How do I enforce a policy on HC3 MCP Server? +

Register the HC3 MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every HC3 MCP Server tool call.

Deterministic rules across all 81 HC3 MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

81 HC3 MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.