handle_click · HoloViz MCP Server MCP: Risk & Policy

WHAT IT DOES

What handle_click does on HoloViz MCP Server

AI agents invoke handle_click to trigger actions in HoloViz 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 handle_click needs a policy

Based on the name alone, 'handle_click' likely triggers a UI interaction or browser action, which falls under Execute. However, the empty description severely limits confidence. Given the sibling tool 'handle_interaction' exists, this may overlap or be a specialization of interaction handling.

From the tool's definition Tool name 'handle_click' suggests triggering a click/interaction event; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

handle_click Rate-limited

handle_click 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": {
    "handle_click": {
      "limits": [
        {
          "counter": "handle_click_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 HoloViz MCP Server, so you can run agents against it safely.

FAQ

Questions about handle_click

What does the handle_click tool do? +

handle_click. It is categorised as a Execute tool in the HoloViz 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 handle_click? +

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

What risk level is handle_click? +

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

Can I rate-limit handle_click? +

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

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

handle_click is provided by the HoloViz MCP Server MCP server (sumayabee/holoviz-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.