MCP Adoption Guide
This guide defines the required MCP baseline for AEEF orchestration implementations.
Policy
- MCP is required for tool-facing integrations in all new examples and starter packs.
- Tool calls must be mediated by agent contract and hook checks.
- Unregistered tools must be denied by default.
Minimum MCP profile
- Tool registry with
tool-id, owner, risk class, and allowed roles. - Pre-tool hook enforcement (
HookContract) for policy and data checks. - Post-tool hook enforcement for trace and evidence capture.
- Gate binding from tool outputs to
GateDecisionartifacts. - Run-ledger logging of all tool invocations.
AEEF mapping
| MCP concern | AEEF control |
|---|---|
| Tool registration | PRD-STD-017 skill/tool governance |
| Tool authorization | AgentContract allowed_tools |
| Tool invocation checks | HookContract pre-phase policy checks |
| Tool output validation | GateDecision criteria |
| Tool traceability | RunLedgerEntry tools_used + artifact_refs |
Implementation note
Use the protocol mapping guide for translation between AEEF schema fields and MCP payload-level metadata.