mcp/policy-aware-actions #13

New issue

Closed

opened 2026-05-09 23:25:16 +02:00 by codex · 1 comment

codex commented

2026-05-09 23:25:16 +02:00

Collaborator

Parent: #2
Wave: 2 - Board Maturity
Depends on: #10, #12

Summary

Teach MCP action tools to return policy warnings before or alongside narrow mutations.

Scope

Add policyWarnings to create/move/link results where relevant.
Warn on WIP exceeded, blocked card, and policy mismatch.
Keep allowed direct actions narrow: create, move, comment, relation link/unlink when approved.
Route broader operations to proposals.

Non-goals

No hard policy enforcement in v1.
No autonomous repair or reprioritization.
No hidden board restructuring.

Acceptance Criteria

Moving into a full column returns a WIP warning.
Moving a blocked card returns a blocked-card warning.
Policy mismatch is visible to Iskra and can be explained to Piotr.
Mutation audit still records action result and warnings.

Tests / Smoke

MCP/API tests for warning shapes.
Smoke for move into Doing with advisory WIP limit.
Regression tests for normal create/move/comment paths.

Rollback

Ignore policyWarnings client-side and keep existing action behavior.

Owner Gates

Owner approval before enabling policy-aware warnings in production MCP responses if clients depend on strict schemas.

Parent: #2 Wave: 2 - Board Maturity Depends on: #10, #12 ## Summary Teach MCP action tools to return policy warnings before or alongside narrow mutations. ## Scope - Add `policyWarnings` to create/move/link results where relevant. - Warn on WIP exceeded, blocked card, and policy mismatch. - Keep allowed direct actions narrow: create, move, comment, relation link/unlink when approved. - Route broader operations to proposals. ## Non-goals - No hard policy enforcement in v1. - No autonomous repair or reprioritization. - No hidden board restructuring. ## Acceptance Criteria - Moving into a full column returns a WIP warning. - Moving a blocked card returns a blocked-card warning. - Policy mismatch is visible to Iskra and can be explained to Piotr. - Mutation audit still records action result and warnings. ## Tests / Smoke - MCP/API tests for warning shapes. - Smoke for move into Doing with advisory WIP limit. - Regression tests for normal create/move/comment paths. ## Rollback Ignore `policyWarnings` client-side and keep existing action behavior. ## Owner Gates Owner approval before enabling policy-aware warnings in production MCP responses if clients depend on strict schemas.

codex referenced this issue

2026-05-09 23:25:23 +02:00

web/blocked-and-policy-cues #14

codex referenced this issue

2026-05-09 23:27:13 +02:00

[meta] Kan-ductor maturity waves #2

codex referenced this issue from a pull request that will close it,

2026-05-10 00:55:40 +02:00

feat(mcp): return policy warnings for agent actions #37

codex commented

2026-05-10 00:55:48 +02:00

Author

Collaborator

PR gotowy: #37 mcp/policy-aware-actions

Zakres:

create_card i move_card zwracają advisory policyWarnings,
warningi obejmują WIP exceeded, blocked card, entry/exit policy, agentMovePolicy: warn i proposal_required,
wynik z warningami trafia też do agent_audit_event.result, więc Iskra może później wyjaśnić, co się stało,
MCP opisy narzędzi mówią wprost, że create/move mogą zwracać policyWarnings,
bez twardego blokowania i bez poszerzania write surface.

Walidacja:

pnpm --filter @kan/db build
pnpm --filter @kan/api build
pnpm --filter @kan/api typecheck
pnpm --filter @kan/db typecheck
pnpm --filter @kan/mcp typecheck
pnpm --filter @kan/api test -- integration-tests/agent.integration.test.ts agent.test.ts integration-tests/card-relations.integration.test.ts integration-tests/list-policies.integration.test.ts
pnpm --filter @kan/api test -- integration-tests/agent.integration.test.ts agent.test.ts
pnpm exec prettier --check packages/db/src/repository/card.repo.ts packages/api/src/routers/agent.ts packages/api/integration-tests/agent.integration.test.ts packages/mcp/src/index.ts docs/agent-mcp-contract.md
git diff --check

Uwagi:

proposal_required jest teraz mocnym sygnałem do wyjaśnienia/proposal-first, ale nie blokadą runtime.
Nie dotykałem produkcyjnych tokenów, sekretów ani deploya.

PR gotowy: #37 `mcp/policy-aware-actions` Zakres: - `create_card` i `move_card` zwracają advisory `policyWarnings`, - warningi obejmują WIP exceeded, blocked card, entry/exit policy, `agentMovePolicy: warn` i `proposal_required`, - wynik z warningami trafia też do `agent_audit_event.result`, więc Iskra może później wyjaśnić, co się stało, - MCP opisy narzędzi mówią wprost, że create/move mogą zwracać `policyWarnings`, - bez twardego blokowania i bez poszerzania write surface. Walidacja: - `pnpm --filter @kan/db build` - `pnpm --filter @kan/api build` - `pnpm --filter @kan/api typecheck` - `pnpm --filter @kan/db typecheck` - `pnpm --filter @kan/mcp typecheck` - `pnpm --filter @kan/api test -- integration-tests/agent.integration.test.ts agent.test.ts integration-tests/card-relations.integration.test.ts integration-tests/list-policies.integration.test.ts` - `pnpm --filter @kan/api test -- integration-tests/agent.integration.test.ts agent.test.ts` - `pnpm exec prettier --check packages/db/src/repository/card.repo.ts packages/api/src/routers/agent.ts packages/api/integration-tests/agent.integration.test.ts packages/mcp/src/index.ts docs/agent-mcp-contract.md` - `git diff --check` Uwagi: - `proposal_required` jest teraz mocnym sygnałem do wyjaśnienia/proposal-first, ale nie blokadą runtime. - Nie dotykałem produkcyjnych tokenów, sekretów ani deploya.