[shiju-nv]

Summary

Keep MCP tool selectors intact through agent proposals and approval. Show their
scope in CLI and Draft review, and require manual approval when the prover cannot
model MCP permissions.

Related Issue

Closes #4679

Changes

• Preserve supported selectors and versions; reject unsupported proposal fields.
• Display allow/deny selectors safely in CLI and TUI Draft review.
• Mark MCP policies unsupported by the prover and refresh cached clean verdicts
  before approval.

Release Notes

Target the next minor release. Unsupported proposal fields now return an error.
MCP policies require human review even in automatic mode.

Testing

• Six targeted tests and faulty-base/head regression controls pass.
• Unit regressions added.
• Hosted E2E for the updated head (pending; test:e2e enabled).

Formatting passes. Local Clippy is deferred to hosted CI.

Checklist

• Conventional Commits.
• Signed off (DCO).
• Existing advisor guidance updated.

[github-actions]

Compatibility review (advisory)

New or updated breaking changes; see the full report for all findings.

1. api-behavior — No explicit risk acceptance found

POST /v1/proposals changed unsupported fields such as endpoint path from silently ignored during parsing to 400 invalid_proposal.

• Impact: Existing agents that relied on the documented ignore behavior receive no accepted chunk IDs until they remove those fields.
• Action: Keep ignoring unsupported fields in v0.1.5 while retaining newly supported selectors, or defer strict rejection to a minor release with notice and removal guidance.
• PR: fix(policy)!: keep MCP tool selectors in agent proposals #4736

Review details

• Execution: complete
• Candidate: PR #4736 (34b098d8506161d35c549afd3bf868d2119e29d7)
• Baseline: 7417f75384a02a12b30b736cc185bb08b814bd40 (7417f75384a02a12b30b736cc185bb08b814bd40)
• Reviewed: rust-sdk, python-sdk, go-sdk, typescript-sdk, api-behavior, cli, configuration, policy, helm, state

Advisory review; publication gates are unchanged.

Branch check run

[github-actions]

Label test:e2e applied for 513efa8. Open the existing run and click Re-run all jobs to execute with the label set. The run will execute the standard E2E suite after building the required gateway, sandbox, and supervisor images once. The matching required CI gate status on this PR will flip green automatically once the run finishes.

[github-actions]

Compatibility review (advisory)

New or updated breaking changes; see the full report for all findings.

2. api-behavior — No explicit risk acceptance found

proposal_approval_mode=auto now leaves otherwise eligible proposals pending whenever either effective policy contains protocol: mcp, instead of approving them automatically.

• Impact: Unattended agents in sandboxes with existing MCP rules receive pending instead of approved even for unflagged, credential-free REST proposals.
• Action: Defer mandatory MCP review to a minor release with explicit guidance for unattended callers to handle pending proposals and obtain manual approval.
• PR: fix(policy)!: keep MCP tool selectors in agent proposals #4736

Review details

• Execution: complete
• Candidate: PR #4736 (efee9be329f1148db12a67e3143f6cf4032b9497)
• Baseline: cc0642fa8955be9db480937193693968ada92a49 (cc0642fa8955be9db480937193693968ada92a49)
• Reviewed: rust-sdk, python-sdk, go-sdk, typescript-sdk, api-behavior, cli, configuration, policy, helm, state

Advisory review; publication gates are unchanged.

Branch check run