The First Adapter Test Should Prove Tool Permission Parity

The first adapter test should prove tool-permission parity because shared tooling becomes dangerous when adapters flatten security differences.

Shared tools are only safe when every adapter path respects the same permission boundary. If one path flattens that boundary, the system stops behaving predictably.

First prove parity for

• Allowed and denied tool calls.
• Audit visibility.
• Error reporting when access is blocked.

Use the adapter system, AuthGuardian, and integration guide to validate permission parity.