MCP: rota writes take no acting_user #120

New issue

Closed

opened 2026-08-18 10:45:23 +00:00 by nalum · 1 comment

nalum commented

2026-08-18 10:45:23 +00:00

Owner

From the surface parity report (2026-08-18), defect 9.

set_rota_slot and override_day attribute the mutation to the API-key credential itself, unlike the other reward-adjacent MCP writes which accept acting_user. MEAL_ASSIGNED notifications will name the credential principal instead of the person who asked.

Where: internal/mcp/tools.go.

Fix: accept acting_user on both rota write tools, same as complete_item and friends.

From the surface parity report (2026-08-18), defect 9. `set_rota_slot` and `override_day` attribute the mutation to the API-key credential itself, unlike the other reward-adjacent MCP writes which accept `acting_user`. MEAL_ASSIGNED notifications will name the credential principal instead of the person who asked. Where: `internal/mcp/tools.go`. Fix: accept `acting_user` on both rota write tools, same as `complete_item` and friends.

nalum added the

bug

label

2026-08-18 10:45:23 +00:00

nalum referenced this issue

2026-08-18 11:22:44 +00:00

Order of work for the open backlog (#107–#136) #137

nalum referenced this issue from a commit

2026-08-18 12:47:24 +00:00

fix(mcp): honest verbs on complete_item, rota writes and update_event

nalum referenced this issue

2026-08-18 12:47:36 +00:00

fix: honest MCP verbs — reopen, rota attribution, event clears #142

nalum commented

2026-08-18 16:46:46 +00:00

Author

Owner

Delivered in PR #142 (merged): the MCP rota write tools now take acting_user, and the audit trail records actor=acting user with subject=the API key. Verified over a live /mcp session.

nalum closed this issue

2026-08-18 16:46:46 +00:00