Skip to content

Manual validation: MCP permissions for Loki and Eitri tools #415

Description

@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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions