create_quickapp_file · HC3 MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_quickapp_file does on HC3 MCP Server

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

WHY IT NEEDS A POLICY

Why create_quickapp_file needs a policy

This tool creates new files (source code for QuickApps) rather than reading, executing, or destructively deleting data. File creation is reversible via deletion and does not directly trigger home automation actions. However, severity is elevated to medium because created QuickApp files could contain malicious code that executes within the HC3 system, affecting connected smart home devices.

From the tool's definition Tool name 'create_quickapp_file' and description 'Create a new source file for a QuickApp' indicate file creation. QuickApp files are code/configuration files in Fibaro's home automation system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_quickapp_file Rate-limited

create_quickapp_file stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_quickapp_file": {
      "limits": [
        {
          "counter": "create_quickapp_file_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 create_quickapp_file

What does the create_quickapp_file tool do? +

Create a new source file for a QuickApp. It is categorised as a Write tool in the 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 create_quickapp_file? +

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

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

Can I rate-limit create_quickapp_file? +

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

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

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