Get Interceptor Metadata
get_interceptor_metadataRetrieve metadata for HTTP Toolkit interceptors to identify available targets like Docker containers, Android devices, and JVM processes for traffic inspection.
Instructions
Get detailed metadata for a specific interceptor. Returns available targets like Docker containers, Android devices, JVM processes, etc.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Interceptor ID (e.g. "fresh-chrome", "android-adb", "docker-attach", "android-frida", "ios-frida", "attach-jvm") | |
| subId | No | Sub-ID for more specific metadata (e.g. a Frida host ID to get its app targets) |
Implementation Reference
- src/httptoolkit-client.ts:91-99 (handler)The implementation of the getInterceptorMetadata method, which makes the HTTP request to fetch metadata.
async getInterceptorMetadata( id: string, subId?: string ): Promise<{ interceptorMetadata: unknown }> { const path = subId ? `/interceptors/${encodeURIComponent(id)}/metadata/${encodeURIComponent(subId)}` : `/interceptors/${encodeURIComponent(id)}/metadata`; return this.request('GET', path); } - src/index.ts:102-114 (registration)The MCP tool registration for 'get_interceptor_metadata'.
server.registerTool( 'get_interceptor_metadata', { title: 'Get Interceptor Metadata', description: 'Get detailed metadata for a specific interceptor. Returns available targets like Docker containers, Android devices, JVM processes, etc.', inputSchema: z.object({ id: z.string().describe('Interceptor ID (e.g. "fresh-chrome", "android-adb", "docker-attach", "android-frida", "ios-frida", "attach-jvm")'), subId: z.string().optional().describe('Sub-ID for more specific metadata (e.g. a Frida host ID to get its app targets)'), }), }, async ({ id, subId }) => jsonResult(await client.getInterceptorMetadata(id, subId)) );