rerender_artifact · Web Gui MCP: Risk & Policy

WHAT IT DOES

What rerender_artifact does on Web Gui

AI agents invoke rerender_artifact to trigger actions in Web Gui. 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 rerender_artifact needs a policy

Based on the tool name and server context, this tool likely triggers a re-rendering operation of an existing artifact (HTML generation/rendering), which constitutes executing an external operation. The empty description lowers confidence. Rendering could involve write-like side effects (updating stored artifact) or execute-like operations (running rendering pipeline).

From the tool's definition Tool name 'rerender_artifact' and server description mentions 'HTML generation and rendering, storing artifacts in memory'. Description is empty/uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rerender_artifact Rate-limited

rerender_artifact 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": {
    "rerender_artifact": {
      "limits": [
        {
          "counter": "rerender_artifact_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 Web Gui, so you can run agents against it safely.

FAQ

Questions about rerender_artifact

What does the rerender_artifact tool do? +

rerender_artifact. It is categorised as a Execute tool in the Web Gui MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on rerender_artifact? +

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

What risk level is rerender_artifact? +

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

Can I rate-limit rerender_artifact? +

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

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

rerender_artifact is provided by the Web Gui MCP server (thehzuo/gui-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.