handle_interaction · HoloViz MCP Server MCP: Risk & Policy

WHAT IT DOES

What handle_interaction does on HoloViz MCP Server

AI agents invoke handle_interaction 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_interaction needs a policy

The tool name implies handling some form of user interaction, likely triggering actions in the visualization context. The sibling tool 'handle_click' reinforces this interpretation — both likely execute event-driven operations. However, the empty description significantly reduces confidence.

From the tool's definition Tool name 'handle_interaction' and sibling tool 'handle_click' suggest triggering external operations or UI interactions; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

handle_interaction Rate-limited

handle_interaction 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_interaction": {
      "limits": [
        {
          "counter": "handle_interaction_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_interaction

What does the handle_interaction tool do? +

handle_interaction. 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_interaction? +

Register the HoloViz MCP Server MCP server in PolicyLayer and add a rule for handle_interaction: 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_interaction? +

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

Can I rate-limit handle_interaction? +

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

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

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