update_quickapp_file · HC3 MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_quickapp_file does on HC3 MCP Server

AI agents use update_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 update_quickapp_file needs a policy

This tool modifies existing QuickApp source code reversibly. While it doesn't delete data (thus not Destructive), updating application code in a smart home system poses significant risk: malicious QuickApp modifications could alter device behavior, disable security features, or create backdoors.

From the tool's definition Tool name 'update_quickapp_file' and description 'Update an existing QuickApp source file' indicate modification of existing data (QuickApp code). The term 'update' is characteristic of Write operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_quickapp_file Rate-limited

update_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": {
    "update_quickapp_file": {
      "limits": [
        {
          "counter": "update_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 update_quickapp_file

What does the update_quickapp_file tool do? +

Update an existing QuickApp source file. 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 update_quickapp_file? +

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

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

Can I rate-limit update_quickapp_file? +

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

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

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