trigger_vscode_reload · MCP Jupyter Complete MCP

WHAT IT DOES

What trigger_vscode_reload does on MCP Jupyter Complete

AI agents invoke trigger_vscode_reload to trigger actions in MCP Jupyter Complete. 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 trigger_vscode_reload needs a policy

This tool executes an action on an external system (VS Code) to reload a file. While not destructive by itself (the reload is reversible and does not delete data), it is an Execute category action because it triggers an external operation.

From the tool's definition Tool description states 'Trigger VS Code to reload the notebook file' — directly triggers an external operation (VS Code reload) whose effects depend on the current notebook state and context.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

trigger_vscode_reload Rate-limited

trigger_vscode_reload 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": {
    "trigger_vscode_reload": {
      "limits": [
        {
          "counter": "trigger_vscode_reload_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 MCP Jupyter Complete, so you can run agents against it safely.

FAQ

Questions about trigger_vscode_reload

What does the trigger_vscode_reload tool do? +

Trigger VS Code to reload the notebook file. It is categorised as a Execute tool in the MCP Jupyter Complete MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on trigger_vscode_reload? +

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

What risk level is trigger_vscode_reload? +

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

Can I rate-limit trigger_vscode_reload? +

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

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

trigger_vscode_reload is provided by the MCP Jupyter Complete MCP server (tofunori/mcp-jupyter-complete). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.