Optionalmessage: stringOptionalmessage: stringOptionaloptions: ErrorOptionsOptionalcauseOptionalstackStaticstackThe Error.stackTraceLimit property specifies the number of stack frames
collected by a stack trace (whether generated by new Error().stack or
Error.captureStackTrace(obj)).
The default value is 10 but may be set to any valid JavaScript number. Changes
will affect any stack trace captured after the value has been changed.
If set to a non-number value, or set to a negative number, stack traces will not capture any frames.
StaticcaptureCreates a .stack property on targetObject, which when accessed returns
a string representing the location in the code at which
Error.captureStackTrace() was called.
const myObject = {};
Error.captureStackTrace(myObject);
myObject.stack; // Similar to `new Error().stack`
The first line of the trace will be prefixed with
${myObject.name}: ${myObject.message}.
The optional constructorOpt argument accepts a function. If given, all frames
above constructorOpt, including constructorOpt, will be omitted from the
generated stack trace.
The constructorOpt argument is useful for hiding implementation
details of error generation from the user. For instance:
function a() {
b();
}
function b() {
c();
}
function c() {
// Create an error without stack trace to avoid calculating the stack trace twice.
const { stackTraceLimit } = Error;
Error.stackTraceLimit = 0;
const error = new Error();
Error.stackTraceLimit = stackTraceLimit;
// Capture the stack trace above function b
Error.captureStackTrace(error, b); // Neither function c, nor b is included in the stack trace
throw error;
}
a();
OptionalconstructorOpt: FunctionStaticprepare
Differential record/replay (Phase 10 / D1).
mcpwn diff <golden-session.jsonl> [options] -- [args...]
mcpwn diff <golden-session.jsonl> --http [options]
Replays the client->server requests captured in a golden session JSONL against a (possibly updated) server, captures the LIVE responses, and diffs them vs the golden responses — surfacing changed shapes/values, added/removed tools or fields, and NEWLY-INTRODUCED injection surfaces (detectors run over the live responses; any finding absent from the golden run is reported).
A golden session is any JSONL recorded by mcpwn (the proxy's
--log, ormcpwn scan --log <file>): each line carriesdirection,kindand the exactrawwire bytes, so we can both replay the requests and recover the golden responses by JSON-RPC id.It REUSES scan.ts's MCP client (handshake/id-correlation/ping/timeouts/clean shutdown) so a drifted or non-responding server can never hang the diff: every request is bounded by a per-call timeout and the target is always killed on exit. Normalising volatile fields (ids, timestamps, a configurable
--ignorelist) before diffing keeps non-determinism from showing up as false drift.