[pramodbn27]

Docs-only notes for MCP 0.5.0 hosted access control: per-key tool policies enforced at dispatch, revocation applied to queued calls, and MCP-local mcp.access-decision.v1 evidence. No dependency, pin or runtime change in this repo, and no release needed. The links to the v0.5.0 tag will resolve once MCP 0.5.0 is tagged; this PR merges after that.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-31T13:19:27.245540Z	14c0964	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[Copilot]

🟡 Changes recommended

Active documentation inaccuracies remain about which access-control outcomes emit dispatch/completion records and how those records relate to the decision schema.

4 open issues

• Limit dispatch and completion logs to allowed calls · New
• Limit dispatch and completion logs to allowed calls · New
• Limit dispatch and completion logs to allowed calls · New
• Separate access-decision schema from dispatch and completion logs · New

What changed in this PR

This docs-only pull request documents MCP 0.5.0 hosted access-control compatibility without changing runtime behavior, dependencies, pins, or release metadata.

Changes:

• Documents per-key policies, expiry, dispatch-time enforcement, revocation behavior, and MCP-local evidence.
• Adds a dedicated hosted access-control compatibility guide.
• Links the guide from the README and roadmap while clarifying unchanged Evals APIs and report contracts.

File	Summary	Review notes
ROADMAP.md	Adds the MCP 0.5.0 hosted access-control roadmap entry.	Qualify dispatch/completion evidence as applying to allowed calls, and document that core.access_status remains callable after policy expiry unless explicitly denied.
README.md	Adds user-facing MCP 0.5.0 compatibility notes and a guide link.	Qualify dispatch/completion evidence as applying to allowed calls, and document the core.access_status expiry exception.
docs/​mcp-0.5-access-control.md	Provides detailed hosted access-control and Evals compatibility guidance.	Qualify allowed-call evidence, document the core.access_status expiry exception, and distinguish mcp.access-decision.v1 denial/revocation records from separate allowed-call dispatch/completion records.

_{Review effort: Lite}

[Copilot]

🔵 Needs a closer look

Three documentation references inaccurately describe the hosted policy’s single-task task_id as a general task scope, so its exact semantics need clarification.

No open issues 🎉

3 previously missed issues

In code that hasn't changed since last review

Describe task_id as the single delegated task

README.md:938

The hosted policy field is task_id, which identifies the single task the key is delegated to; it is not a general task scope. Calling it a “task scope” can mislead readers into expecting a set or range of tasks. Please name the field and describe its exact semantics.

Describe task_id as the single delegated task

ROADMAP.md:592

The hosted policy field is task_id, which identifies the single task the key is delegated to; it is not a general task scope. Calling it a “task scope” can mislead readers into expecting a set or range of tasks. Please name the field and describe its exact semantics.

Describe task_id as the single delegated task

docs/​mcp-0.5-access-control.md:3

The hosted policy field is task_id, which identifies the single task the key is delegated to; it is not a general task scope. Calling it a “task scope” can mislead readers into expecting a set or range of tasks. Please name the field and describe its exact semantics.

4 resolved since last review

• Separate access-decision schema from dispatch and completion logs
• Limit dispatch and completion logs to allowed calls
• Limit dispatch and completion logs to allowed calls
• Limit dispatch and completion logs to allowed calls

_{Review effort: Lite}