Member Junction
    Preparing search index...

    Interface RemoteOpServerContext

    Server-side execution context handed to BaseRemotableOperation.ExecuteServer (and through it to Authorize and InternalExecute) when a Remote Operation runs in-process on the server. It carries everything a server implementation needs without coupling the operation to any transport.

    interface RemoteOpServerContext {
        apiKeyHash?: string;
        clientIp?: string;
        emitProgress: (progress: RemoteOpProgress) => void;
        handle?: string;
        provider: IMetadataProvider;
        requestOrigin?: string;
        sessionId?: string;
        user: UserInfo;
    }
    Index

    Properties

    apiKeyHash? clientIp? emitProgress handle? provider requestOrigin? sessionId? user

    Properties

    apiKeyHash?: string

    SHA-256 hash of the caller's MJ API key when invoked via mj_sk_* API key / MCP.

    clientIp?: string

    Caller's network IP address (req.ip) when invoked over HTTP/GraphQL. Suitable for abuse rate-limiting and forensic audit logging; never use as an identity check.

    emitProgress: (progress: RemoteOpProgress) => void

    Emits a streaming progress update for LongRunning operations (no-op for Sync).

    handle?: string

    Opaque handle for the backing run (e.g. a ProcessRunID), when one has been created.

    provider: IMetadataProvider

    The provider that owns this execution (use this for data access — never new Metadata()).

    requestOrigin?: string

    Normalized HTTP Origin header (scheme://host[:port], lowercased, no trailing slash) when the operation arrived over HTTP/GraphQL. Undefined for in-process calls or requests lacking an Origin header — origin allowlist checks must fail closed on undefined.

    sessionId?: string

    Caller's authenticated session ID when available from the server transport.

    user: UserInfo

    The resolved acting user for permission-scoped data work.

    Settings

    Member Visibility

    On This Page

    Properties