feat(mcp): expose paper-named tools (aflock_authorize/attest/check_limits/delegate)

[manzil-infinity180]

Summary

Paper §3.3 names four MCP tools — aflock_authorize, aflock_attest, aflock_check_limits, aflock_delegate. None of them exist. Anyone reading the paper and probing the server immediately hits tool not found.

Problem

Tools registered in internal/mcp/server.go:117-203 are:
bash, check_tool, get_identity, get_policy, get_session, get_token, read_file, sign_attestation, write_file.

Live MCP probe over UDS (PR #88 socket):

[paper:aflock_authorize]    tool 'aflock_authorize' not found
[paper:aflock_attest]       tool 'aflock_attest' not found
[paper:aflock_check_limits] tool 'aflock_check_limits' not found
[paper:aflock_delegate]     tool 'aflock_delegate' not found

Functionally check_tool ≈ authorize, sign_attestation ≈ attest. aflock_check_limits and aflock_delegate have no equivalent at all — CheckLimits is library-internal (policy/evaluator.go:1001) and delegation lives only in hooks (state/propagation.go).

Expected (paper §3.3)

aflock_authorize: Request authorization for an action
aflock_attest: Record an action (server signs attestation)
aflock_check_limits: Query remaining budget
aflock_delegate: Create sublayout for sub-agent

Fix sketch

In internal/mcp/server.go:registerTools():

• aflock_authorize → alias handleCheckTool
• aflock_attest → alias handleSignAttestation
• aflock_check_limits (new) → return {remainingSpendUSD, remainingTokensIn, remainingTurns} from state.GetMetrics() − policy.Limits
• aflock_delegate (new) → write propagation record + mint attenuated child JWT (requires new method on auth.TokenIssuer)

Either alias and keep legacy names, or rename and document the migration. aflock_delegate is the only non-trivial one; the other three are wiring.

[Keesan12]

This feels like an enforcement or verification boundary issue. I’d keep the policy decision on the boundary that actually enforces it, then pin the expected behavior with a regression test. This looks like a discovery or config ambiguity; I’d make the active source of truth explicit and fail fast when the connector set is empty or mismatched. A small regression around the exact transition would pay for itself quickly here. If this is useful, I can help turn it into a compact repro checklist or PR shape.

[manzil-infinity180]

Merged into dev via #149. Closing.