MCP Permission Drift Detection

Required inputs

For a manual review: two dated, complete tool inventories; server and tool identities; authentication context; declared actions, resources and recipients; and authority references. Do not include credentials.

Delivered results

A free source-linked comparison worksheet and acceptance checklist. A reviewer records observed declaration differences and unresolved evidence. No new detector or automated comparison executable is delivered.

Decision boundary

Mark the comparison unestablished when identities, authorisation context, pagination coverage or timestamps cannot be aligned. Changes alone do not prove effective permission drift.

• Unvalidated comparison pilot; no paid activation, price, executable entitlement or recurring service.
• No automatic MCP polling, live permission inspection, monitoring, drift detection guarantee or runtime enforcement.

Manual comparison worksheet

1. Record both capture dates and exact server, tool and version identifiers.
2. Establish comparable authentication context and complete pagination; retain source references without credentials.
3. Compare declared actions, resources, recipients and authority references manually; record additions, removals and changes.
4. Separate tool-list differences from verified effective-permission changes; record unresolved evidence.
5. Require schema validation, deterministic comparison tests, adversarial fixtures and separate release approval before any new executable or paid activation.

For each tool, record: before/after identity and capture time; authentication context; action, resource and recipient changes; source reference; unresolved evidence; reviewer conclusion. Use “unestablished” wherever the comparison lacks evidence. This worksheet is free to use and contains no automated comparison logic.

Source evidence

Reused dated documentation reviews retain their original source dates, versions, exclusions and provenance. Compilation does not refresh sources or expand executable profiles.

• MCP: Tool inventory depends on request authority — reviewed 2026-10-18. Primary source
• MCP: Tool annotations describe hints, not enforced authority — reviewed 2026-10-18. Primary source
• MCP Registry: Publisher namespace is a limited identity check — reviewed 2026-10-18. Primary source

This workflow’s JSON manifest and content hash

Pilot availability

No purchase path or price exists for this pilot. Read the supporting free evidence. Separate validation and approval are required before any executable or paid activation.