Manual validation: MCP permissions for Loki and Eitri tools

[DylenTurnbull]

Summary

After #403, manually validate MCP permission behavior across the full supported tool set for Loki and Eitri.

Validation scope

For each supported Loki and Eitri MCP tool:

• invoke the tool through a remote Council session;
• confirm the remote approval request is shown and can be answered;
• verify the tool completes after approval;
• verify decline remains declined;
• verify Loki and Eitri Explore remain within Mjolnir’s read-only boundaries.

Expected

Remote MCP approval should work for every supported Loki and Eitri tool without restoring Council-owned permission injection or elevating role access.

Notes

This is a manual testing follow-up for #403, not a feature request or implementation task.

Related: #403, #412

[DylenTurnbull]

Validated fix/420-scoped-mcp-approval at 354721f749c0f13eb7094bcf393a85966a33f2c4 through the remote Tailscale UI using isolated disposable fixtures.

Remote approval routing passed for the directly testable MCP commands:

• Loki pull_advice: Allow and Decline
• Eitri code_agent: Allow and Decline
• Eitri code_agent_continue: Allow and Decline
• Eitri code_agent_cancel: Allow and Decline
• Eitri explore_agent: Allow and Decline
• Eitri explore_agents: Allow and Decline

In each case, the expected remote permission dialog appeared. Allow forwarded the request; Decline rejected it before the tool ran. Eitri exploration completed read-only with no fixture changes.

Loki’s internal advise callback was not directly observable in the Council-only scenario, so that item remains inconclusive.

Separate from approval routing: allowed code_agent_continue and code_agent_cancel calls reported that a genuine previously PAUSED Eitri run was not resumable/cancellable. Those are downstream lifecycle findings, not treated as #415 approval-routing failures. No follow-up issues have been opened.

Cleanup completed: test server stopped, disposable fixtures removed, and source worktrees remained clean.