fix: update MCP access docs to reflect per-key grants support #118

Merged
abiba-bot merged 3 commits from fix/infra-mcp-per-key-grants-20260918 into master 2026-09-18 18:52:14 +00:00
Owner

PR #117 follow-up (verify PASS-WITH-FINDINGS):

  1. infrastructure-update.prose.md: agent keys now have per-key MCP grants (2026-09-18), struck-through old limitation, marked Migration Path as COMPLETED

  2. hermes-config-template.prose.md: removed hedge, stated fact that per-key MCP grants verified 2026-09-18

Resolves the contradiction between files on MCP access.

PR #117 follow-up (verify PASS-WITH-FINDINGS): 1. infrastructure-update.prose.md: agent keys now have per-key MCP grants (2026-09-18), struck-through old limitation, marked Migration Path as COMPLETED 2. hermes-config-template.prose.md: removed hedge, stated fact that per-key MCP grants verified 2026-09-18 Resolves the contradiction between files on MCP access.
abiba-bot added 1 commit 2026-09-18 18:34:58 +00:00
fix: update MCP access docs to reflect per-key grants support
PR Pipeline — Authorize → Validate → Review → Merge / auth (pull_request) Successful in 5s
PR Pipeline — Authorize → Validate → Review → Merge / validate (pull_request) Successful in 9s
PR Pipeline — Authorize → Validate → Review → Merge / lint (pull_request) Successful in 6s
PR Pipeline — Authorize → Validate → Review → Merge / ai-review (pull_request) Successful in 6s
PR Pipeline — Authorize → Validate → Review → Merge / gate (pull_request) Successful in 1s
c0454811bb
PR #117 follow-up (verify PASS-WITH-FINDINGS):

1. infrastructure-update.prose.md:
   - Update access table: agent keys now have per-key MCP grants (2026-09-18)
   - Strike-through old limitation: per-key grants now work
   - Mark Migration Path as COMPLETED 2026-09-18

2. hermes-config-template.prose.md:
   - Remove hedge ('may have been upgraded')
   - State fact: per-key MCP grants verified 2026-09-18

This resolves the contradiction where one file asserted per-key
MCP access and the other denied it.
abiba-bot added 1 commit 2026-09-18 18:38:46 +00:00
fix: consolidate PR #117 Rule 15 wording fix
PR Pipeline — Authorize → Validate → Review → Merge / auth (pull_request) Successful in 12s
PR Pipeline — Authorize → Validate → Review → Merge / validate (pull_request) Successful in 3s
PR Pipeline — Authorize → Validate → Review → Merge / lint (pull_request) Successful in 3s
PR Pipeline — Authorize → Validate → Review → Merge / ai-review (pull_request) Successful in 3s
PR Pipeline — Authorize → Validate → Review → Merge / gate (pull_request) Successful in 1s
f4f8a4cab8
Add the audit-hermes-config.py Rule 15 wording fix from PR #117:
- Violation message now reads 'URL is incorrect: <url> (expected: <expected>)'
- Detection logic unchanged
- Matches URL and not-in-known-list branches remain byte-identical

This consolidates relay #779 into a single PR (#118).
abiba-bot added 1 commit 2026-09-18 18:49:25 +00:00
fix: correct field name to allowed_mcp_servers
PR Pipeline — Authorize → Validate → Review → Merge / auth (pull_request) Successful in 2s
PR Pipeline — Authorize → Validate → Review → Merge / validate (pull_request) Successful in 8s
PR Pipeline — Authorize → Validate → Review → Merge / ai-review (pull_request) Successful in 5s
PR Pipeline — Authorize → Validate → Review → Merge / lint (pull_request) Successful in 5s
PR Pipeline — Authorize → Validate → Review → Merge / gate (pull_request) Successful in 2s
f77d6ca1d1
PR #118 finding F1 (low): The deployed LiteLLM on CT 116 uses
allowed_mcp_servers (193 occurrences in installed package), not
bare allowed_mcp. One-word doc fix.
abiba-bot merged commit 43e891e679 into master 2026-09-18 18:52:14 +00:00
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SyslogSolution/prose-contracts#118