restart_quickapp · HC3 MCP Server MCP: Risk & Policy

WHAT IT DOES

What restart_quickapp does on HC3 MCP Server

AI agents invoke restart_quickapp to trigger actions in 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 restart_quickapp needs a policy

Restarting a QuickApp triggers an external operation (system restart) whose effects depend on which QuickApp is targeted and the current system state. This is a code/process execution action that can disrupt home automation workflows, potentially affecting dependent automations, integrations, or user routines.

From the tool's definition Tool name 'restart_quickapp' and description 'Restart a QuickApp' indicate execution of a restart operation on a QuickApp component within a Fibaro Home Center 3 smart home system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

restart_quickapp Rate-limited

restart_quickapp 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": {
    "restart_quickapp": {
      "limits": [
        {
          "counter": "restart_quickapp_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 HC3 MCP Server, so you can run agents against it safely.

FAQ

Questions about restart_quickapp

What does the restart_quickapp tool do? +

Restart a QuickApp. It is categorised as a Execute tool in the 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 restart_quickapp? +

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

What risk level is restart_quickapp? +

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

Can I rate-limit restart_quickapp? +

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

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

restart_quickapp is provided by the HC3 MCP Server MCP server (jangabrielsson/hc3_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.