fix(entitlements): gate paid MCP tools (send_invoice/agi_submit/vat_declaration_submit) server-side (#846)
The HTTP routes call requireCapability at every paid chokepoint, but the MCP/agent path bypassed the paywall entirely: the three external-service tools stage operations whose commit calls the email / Skatteverket services directly, with no capability check. After the 2026-07-07 trial cutover a trial-connected non-payer using the gnubok MCP connector could still send invoice emails and file AGI/VAT. Close the gap with two layers, mirroring the existing TOOL_SCOPE_MAP gate: - Dispatch gate (mcp-server/server.ts): MCP_TOOL_CAPABILITY_MAP, checked right after the scope check, blocks a non-entitled company before any pending op is staged. Emits errorKind='capability_denied' telemetry. - Commit-time gate (commitPendingOperation): PAID_OPERATION_CAPABILITY_MAP, checked before the atomic claim. The real external-service chokepoint — applies to the MCP approve tool AND the UI approval path, and closes the trial-connected-token window (the grant has expired by commit time). A blocked op stays 'pending', so it is re-approvable once the company subscribes. Adds a transport-free capabilityBlockedError() helper (shared bilingual copy) and locks both maps with tests (maps, dispatch gate, commit gate). Only the three write/submit tools are gated; SKV read/local tools stay free per the statutory carve-out. No DB/migration change; self-hosted stays all-on. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 4.8
parent
5df6199bd1
commit
db843a7a5b
@@ -53,3 +53,34 @@ export const PAID_CAPABILITIES: readonly CapabilityKey[] = [
|
||||
CAPABILITY.skatteverket,
|
||||
CAPABILITY.email_send,
|
||||
] as const
|
||||
|
||||
/**
|
||||
* Paid MCP tools → required capability. The MCP/agent path is a paid chokepoint
|
||||
* just like the HTTP routes, so the dispatcher gates these the same way it gates
|
||||
* API-key scope (see mcp-server `tools/call`). Only external-service WRITE tools
|
||||
* appear here: send_invoice (email) and the two Skatteverket submissions. The
|
||||
* read/local SKV tools (generate_agi, vat_declaration_validate/status, agi_status)
|
||||
* stay free — the §4 carve-out forbids blocking a statutory filing obligation.
|
||||
*
|
||||
* No MCP tool invokes AI or triggers bank sync, so those PAID capabilities have
|
||||
* no entry here — they are reachable only via already-gated HTTP routes/handlers.
|
||||
*/
|
||||
export const MCP_TOOL_CAPABILITY_MAP: Readonly<Partial<Record<string, CapabilityKey>>> = {
|
||||
gnubok_send_invoice: CAPABILITY.email_send,
|
||||
gnubok_vat_declaration_submit: CAPABILITY.skatteverket,
|
||||
gnubok_agi_submit: CAPABILITY.skatteverket,
|
||||
} as const
|
||||
|
||||
/**
|
||||
* Paid pending-operation types → required capability. Keyed by
|
||||
* `pending_operations.operation_type`. This is the commit-time twin of
|
||||
* MCP_TOOL_CAPABILITY_MAP: it gates the actual external-service call inside
|
||||
* commitPendingOperation, so an operation staged during the trial cannot be
|
||||
* committed once the grant has expired — regardless of caller (MCP approve tool
|
||||
* or the UI approval path). Keep the values in sync with MCP_TOOL_CAPABILITY_MAP.
|
||||
*/
|
||||
export const PAID_OPERATION_CAPABILITY_MAP: Readonly<Partial<Record<string, CapabilityKey>>> = {
|
||||
send_invoice: CAPABILITY.email_send,
|
||||
submit_vat_declaration: CAPABILITY.skatteverket,
|
||||
submit_agi: CAPABILITY.skatteverket,
|
||||
} as const
|
||||
|
||||
Reference in New Issue
Block a user