restart_plugin · HC3 MCP Server MCP: Risk & Policy

WHAT IT DOES

What restart_plugin does on HC3 MCP Server

AI agents invoke restart_plugin 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_plugin needs a policy

Restarting a plugin is an Execute-category action because it triggers an external operation (plugin restart) whose effects depend on which plugin is targeted. While not destructive (data is not deleted), it materially affects system operation, can disrupt active automations and device control, and the blast radius is high in a smart home context where critical devices may depend on the restarted plugin.

From the tool's definition Tool name 'restart_plugin' directly indicates execution of an action that triggers a plugin restart. Description states it will 'Restart a plugin/device', which is an operational action that modifies system state and may impact connected devices and…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

restart_plugin Rate-limited

restart_plugin 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_plugin": {
      "limits": [
        {
          "counter": "restart_plugin_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_plugin

What does the restart_plugin tool do? +

Restart a plugin/device. 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_plugin? +

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

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

Can I rate-limit restart_plugin? +

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

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

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