Limit how long a gateway tool call can run

Abierto
#2,836 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go

Línea de trabajo

Start by tracing the gateway tool call and ordinary MCP client request paths; the issue does not name their files or tests. Read the linked credentials-and-lifecycle.md sections on call duration and pauses, then locate how the client writes requests, reads responses, and holds the send-once claim. Done means bounded call duration and response reads, with timed-out written requests ending as unknown outcomes and never replaying; the scope and fixed-versus-configurable limit still need decisions.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Related: #2536, #2564, #2730, #2731

Problem

A gateway tool call has no time limit on Mecatl's side. A gateway that keeps streaming, or never answers, holds the call open until the run is cancelled, and the call's send-once claim stays held the whole time. This is safe (the call is never sent twice), but a stuck call blocks the run until someone cancels it. The MCP client's ordinary path for MCP servers has the same gap.

Design

What

  • A maximum duration for a gateway tool call on the client side, no shorter than the vMCP's. Decide whether it is fixed or an operator setting.
  • A call that reaches it ends as an unknown outcome, if the request was written, and keeps its send-once claim.
  • A bound on how much of a response the client reads.
  • Decide whether the same limit applies to calls to ordinary MCP servers.

Done when

A gateway that never answers, or streams without end, ends the call at the limit as an unknown outcome, and the call is not sent again.

Lenguaje dominante
Go
Estrellas
309
Forks
29
Merge medio
15 h 56 min
PR fusionados (30 d)
225

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de stacklok/mecatl

Todos los issues de stacklok/mecatl

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.