web_preview_reload

What web_preview_reload does on Yaver

AI agents invoke web_preview_reload to trigger actions in Yaver. 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 web_preview_reload is rated High

This tool executes a command (hot reload) on an external system (web dev server). While the operation itself is reversible and non-destructive, it qualifies as Execute because it runs an action with side effects outside the control plane. The severity is high because a misused trigger could interrupt development workflows, corrupt build state, or cause cascading failures in dependent services.

From the tool's definition Tool description states 'Trigger a hot reload on the active web dev server' — 'trigger' indicates execution of an external operation (hot reload) whose effects depend on which dev server is active.

The rule that runs web_preview_reload safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For web_preview_reload, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "web_preview_reload": {
      "limits": [
        {
          "counter": "web_preview_reload_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about web_preview_reload