High Risk →

excel_launch_addin

Launches Excel with the detected add-in and WebView2 remote debugging enabled. Idempotent per manifest path: re-calling returns the tracked launch instead of spawning a duplicate.

Accepts file system path (cwd)

Part of the Excel Webview2 MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents invoke excel_launch_addin to trigger processes or run actions in Excel Webview2. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

excel_launch_addin can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

excel-webview2.yaml
tools:
  excel_launch_addin:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Excel Webview2 policy for all 59 tools.

Tool Name excel_launch_addin
Category Execute
Risk Level High

View all 59 tools →

Agents calling execute-class tools like excel_launch_addin have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

excel_launch_addin is one of the high-risk operations in Excel Webview2. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the excel_launch_addin tool do? +

Launches Excel with the detected add-in and WebView2 remote debugging enabled. Idempotent per manifest path: re-calling returns the tracked launch instead of spawning a duplicate.. It is categorised as a Execute tool in the Excel Webview2 MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on excel_launch_addin? +

Add a rule in your Intercept YAML policy under the tools section for excel_launch_addin. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Excel Webview2 MCP server.

What risk level is excel_launch_addin? +

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

Can I rate-limit excel_launch_addin? +

Yes. Add a rate_limit block to the excel_launch_addin rule in your Intercept 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 excel_launch_addin completely? +

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

excel_launch_addin is provided by the Excel Webview2 MCP server (@dsbissett/excel-webview2-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.