[docs-scanner] Contradictory information about MCP approval fields in audit records

Abierto Apto para principiantes
  • ¿Algo no está bien?
#26,559 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
1/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
88/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
markdown
Área
documentation

Línea de trabajo

Lee content/manuals/ai/governance/reference/audit-records.md, centrándote en la sección “Approval fields” y su tabla. Aclara qué campos corresponden a las aprobaciones de red y cuáles a las aprobaciones de MCP, manteniendo las descripciones coherentes con el texto. El objetivo se cumple cuando los lectores pueden saber qué campos esperar para cada tipo de aprobación.

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

Descripción

File: content/manuals/ai/governance/reference/audit-records.md

Issue

The "Approval fields" section contains contradictory information about which fields appear in MCP approval records. The prose states:

For MCP approvals, an approved request is evaluated again and recorded with AUDIT_DECISION_APPROVAL_ALLOW, and a declined request is recorded with AUDIT_DECISION_APPROVAL_DENY. Neither record includes approval.approval_request_id or approval.grant_scope.

However, the table immediately below lists:

Field Description
approval.approval_request_id ID that links an approval required record to the record that resolves it.
approval.grant_scope Scope the user accepted. Present only on AUDIT_DECISION_APPROVAL_ALLOW records.

The table descriptions don't distinguish between network and MCP approvals, suggesting these fields are present on all AUDIT_DECISION_APPROVAL_ALLOW records, which contradicts the prose statement that MCP approvals don't include them.

Why this matters

A reader trying to parse MCP approval audit records will be confused about which fields to expect. If they follow the prose, they won't look for these fields. If they follow the table, they'll expect them to be present. This makes it impossible to correctly process MCP approval records.

Suggested fix

Clarify the table to indicate which fields apply to network approvals vs. MCP approvals. For example:

Field Description
approval.approval_request_id ID that links an approval required record to the record that resolves it. Present for network approvals only.
approval.grant_scope Scope the user accepted. Present only on network approval AUDIT_DECISION_APPROVAL_ALLOW records.

Or restructure the section to have separate subsections for network approval fields and MCP approval fields.

Found by nightly documentation quality scanner

Lenguaje dominante
Markdown
Estrellas
4.7k
Forks
8.5k
Merge medio
2 d 13 h
PR fusionados (30 d)
139

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 docker/docs

Todos los issues de docker/docs

Issues similares

Más issues de Documentation

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.