Skip to main content
Glama
yfe404

proxy-mcp

by yfe404
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

proxy_stop

Stop the MITM proxy to end traffic interception while retaining history and CA certificate. Deactivate this session's targets, or pass all=true to stop all sessions' targets.

Instructions

Stop the MITM proxy. Traffic history and CA certificate are retained. Interceptor targets (browsers, containers, spawned processes) activated by THIS MCP session are deactivated; targets belonging to other MCP sessions keep running, though the proxy they were pointed at is gone until someone calls proxy_start again. Pass all=true to deactivate every session's targets (the pre-3.5.3, process-wide behaviour). Over stdio there is one session, so every target is deactivated either way.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
allNoDeactivate every session's interceptor targets, not just this session's (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.5.3
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / all
      Added value: +{
+  "default": false,
+  "description": "Deactivate every session's interceptor targets, not just this session's (default: false)",
+  "type": "boolean"
+}
  2. Addedv1.0.0

TDQS

A4.8/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full behavioral burden and succeeds. It discloses what is retained, what is deactivated, how other sessions' targets behave after the proxy stops, and the subtle all=true process-wide behavior. This is unusually transparent for a stop operation.

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?

Three sentences with no wasted words: the first states the core action and retained state, the second explains session-scoped behavior, and the third resolves the stdio edge case. Information is front-loaded and every sentence earns its place.

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 single-optional-parameter stop operation, the description covers purpose, side effects, cross-session semantics, and the all flag's historical behavior. No output schema is needed to understand what will happen, and nothing essential is missing.

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?

Schema coverage is already 100% with a default and description for 'all,' but the tool description adds crucial meaning: all=true is the pre-3.5.3 process-wide behavior, and under stdio the flag is effectively irrelevant because there is only one session. This is genuinely useful semantic enrichment beyond the schema.

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?

Starts with a clear imperative, 'Stop the MITM proxy,' and immediately specifies the operation's scope through its side effects: traffic history and CA certificate are retained, and interceptor targets are deactivated. The session-based behavior distinguishes it from proxy_start and interceptor_deactivate_all, so an agent can predict exactly what this tool does and does not do.

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?

Provides clear operational context: when to pass all=true, how session ownership affects which targets are deactivated, and the stdio single-session simplification. It does not explicitly name alternatives or say 'use this instead of X,' but the context is strong enough for correct invocation.

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

Deploy Server

Other Tools