open_nubracollector_ui · Nubra MCP Server MCP: Risk & Policy

WHAT IT DOES

What open_nubracollector_ui does on Nubra MCP Server

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

The tool launches a desktop UI application, which constitutes executing an external process. It also initiates live websocket collection workflows, which are ongoing external operations. While it is not directly destructive or financial, launching external processes with session reuse capability has moderate blast radius if misused by an AI agent.

From the tool's definition 'Launch the NubraCollector desktop UI' — this triggers an external desktop application process, which is an execution of an external operation whose effects depend on the current session and runtime environment.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

open_nubracollector_ui Rate-limited

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

FAQ

Questions about open_nubracollector_ui

What does the open_nubracollector_ui tool do? +

Launch the NubraCollector desktop UI for live websocket collection and export workflows. If the current Nubra MCP session is valid, the UI reuses it automatically; otherwise the UI falls back to its own login flow. It is categorised as a Execute tool in the Nubra 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 open_nubracollector_ui? +

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

What risk level is open_nubracollector_ui? +

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

Can I rate-limit open_nubracollector_ui? +

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

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

open_nubracollector_ui is provided by the Nubra MCP Server MCP server (socials-zanskar/nubra-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.