Skip to main content
Glama

interceptor_deactivate_all

Emergency cleanup that kills all active interceptors across all types. Stops browser instances, spawned processes, ADB tunnels, Frida, and cleans Docker.

Instructions

Kill ALL active interceptors across all types. Emergency cleanup — stops all browser instances, kills spawned processes, removes ADB tunnels, detaches Frida, cleans Docker.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool registration and handler for 'interceptor_deactivate_all'. Calls interceptorManager.deactivateAll() to shut down all active interceptors (browser, terminal, Android ADB, Android Frida, Docker).
    server.tool(
      "interceptor_deactivate_all",
      "Kill ALL active interceptors across all types. Emergency cleanup — stops all browser instances, kills spawned processes, removes ADB tunnels, detaches Frida, cleans Docker.",
      {},
      async () => {
        try {
          await interceptorManager.deactivateAll();
          return {
            content: [{
              type: "text",
              text: JSON.stringify({ status: "success", message: "All interceptors deactivated." }),
            }],
          };
        } catch (e) {
          return { content: [{ type: "text", text: JSON.stringify({ status: "error", error: errorToString(e) }) }] };
        }
      },
    );
  • Tool is registered via server.tool() with name 'interceptor_deactivate_all', empty schema {}, and async handler. This is part of the Discovery group of interceptor tools.
    server.tool(
      "interceptor_deactivate_all",
      "Kill ALL active interceptors across all types. Emergency cleanup — stops all browser instances, kills spawned processes, removes ADB tunnels, detaches Frida, cleans Docker.",
      {},
      async () => {
        try {
          await interceptorManager.deactivateAll();
          return {
            content: [{
              type: "text",
              text: JSON.stringify({ status: "success", message: "All interceptors deactivated." }),
            }],
          };
        } catch (e) {
          return { content: [{ type: "text", text: JSON.stringify({ status: "error", error: errorToString(e) }) }] };
        }
      },
    );
  • InterceptorManager.deactivateAll() — iterates all registered interceptors and calls deactivateAll() on each. Collects errors and throws if any interceptor fails during cleanup.
    async deactivateAll(): Promise<void> {
      const errors: string[] = [];
      for (const interceptor of this.interceptors.values()) {
        try {
          await interceptor.deactivateAll();
        } catch (e) {
          errors.push(`${interceptor.id}: ${e}`);
        }
      }
      if (errors.length > 0) {
        throw new Error(`Errors during deactivateAll: ${errors.join("; ")}`);
      }
    }
  • The tool has an empty schema {} meaning it takes no input parameters.
    "Kill ALL active interceptors across all types. Emergency cleanup — stops all browser instances, kills spawned processes, removes ADB tunnels, detaches Frida, cleans Docker.",
    {},
  • Interceptor interface definition — declares the deactivateAll() method that each interceptor type must implement.
    export interface Interceptor {
      readonly id: string;
      readonly name: string;
    
      /**
       * Check if this interceptor can be activated (required tooling exists).
       * Uses dynamic imports — returns false if dependencies are missing.
       */
      isActivable(): Promise<boolean>;
    
      /**
       * Activate interception for a target.
       * Handles proxy config, certificate trust, tunnel setup, etc.
       */
      activate(options: ActivateOptions): Promise<ActivateResult>;
    
      /**
       * Deactivate a specific target by ID.
       */
      deactivate(targetId: string): Promise<void>;
    
      /**
       * Deactivate all active targets. Called during proxy shutdown.
       */
      deactivateAll(): Promise<void>;
    
      /**
       * Get metadata for display: availability, active targets.
       */
      getMetadata(): Promise<InterceptorMetadata>;
    }
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description fully discloses destructive side effects: stops browser instances, kills spawned processes, removes ADB tunnels, detaches Frida, cleans Docker. This is comprehensive and beyond minimal requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise: one sentence with a clear action followed by a list of effects. Front-loaded with the core function. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a parameterless tool with no output schema, the description covers all necessary context: purpose, scope, and specific effects. Nothing missing for effective agent invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has zero parameters, baseline is 4. The description adds significant meaning by clarifying the scope ('ALL'). It effectively replaces any need for parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses specific verb 'Kill' and resource 'ALL active interceptors across all types', and lists concrete actions (stops browsers, kills processes, removes ADB tunnels, detaches Frida, cleans Docker). This clearly distinguishes it from sibling tools like interceptor_android_deactivate or interceptor_kill.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description labels it as 'Emergency cleanup', implying use when you need to stop everything immediately. It does not explicitly state when not to use or provide alternative tools, but the urgency context guides appropriate usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yfe404/proxy-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server