Skip to main content
Glama

deactivate_interceptor

Stop capturing HTTP(S) traffic by deactivating a running interceptor in HTTP Toolkit. Use this tool to end traffic inspection and debugging sessions.

Instructions

Deactivate a running interceptor and stop capturing its traffic

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesInterceptor ID to deactivate
proxyPortYesProxy port the interceptor is active on

Implementation Reference

  • The MCP tool handler for 'deactivate_interceptor', which calls the client method.
    async ({ id, proxyPort }) => {
      const result = await client.deactivateInterceptor(id, proxyPort);
      return jsonResult({ success: result });
    }
  • The client method 'deactivateInterceptor' which executes the GraphQL mutation.
    async deactivateInterceptor(
      id: string,
      proxyPort: number
    ): Promise<boolean> {
      const data = await this.graphql<{ deactivateInterceptor: boolean }>(
        `mutation DeactivateInterceptor($id: ID!, $proxyPort: Int!) {
          deactivateInterceptor(id: $id, proxyPort: $proxyPort)
        }`,
        { id, proxyPort }
      );
      return data.deactivateInterceptor;
    }
  • src/index.ts:116-125 (registration)
    The registration of the 'deactivate_interceptor' tool.
    server.registerTool(
      'deactivate_interceptor',
      {
        title: 'Deactivate Interceptor',
        description: 'Deactivate a running interceptor and stop capturing its traffic',
        inputSchema: z.object({
          id: z.string().describe('Interceptor ID to deactivate'),
          proxyPort: z.number().describe('Proxy port the interceptor is active on'),
        }),
      },

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/fdciabdul/httptoolkit-mcp'

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