logi-approval

logi Agent Approval Gate

logi's Agent Approval Gate lets an AI agent pause and ask a human for explicit approval — via a push notification with Face ID / passkey confirmation on their phone — before performing an action that is expensive, irreversible, or otherwise high-risk. The human sees a plain-language description of the action and a 6-digit number_match code, and taps 승인(approve) or 거절(reject).

What this gate is for

• Changing an ads/marketing budget by more than ~20% or a large absolute amount
• Running migrations or destructive operations on a production database
• Sending bulk email/SMS (e.g. more than 100 messages in one batch)
• Spending above a threshold on any external paid API
• Deploying to production
• Any other action the project owner has flagged as requiring sign-off

If in doubt whether an action qualifies, treat it as high-risk and request approval rather than proceeding silently.

When to call the tool

The bundled logi-approval MCP server exposes two tools, named logi__request_approval and logi__check_approval. Depending on the host, they may appear under a namespaced full name — in Claude Code a plugin-bundled server surfaces them as mcp__plugin_logi-approval_logi-approval__logi__request_approval — so match tools by the trailing name, not the exact prefix.

Call the request-approval tool before executing the risky action, not after. It blocks (or can be polled with the check-approval tool) until the user decides or the request times out.

logi__request_approval({
  action_type: "ads.budget_change",
  title: "Meta 광고 예산 변경",
  body: "500,000 KRW → 5,000,000 KRW 로 10배 증액"
})

Rules:

• If the response status is not "approved", abort the action and tell the user it was rejected or timed out — never proceed anyway.
• Do not batch multiple high-risk actions under one vague approval request; each distinct risky action gets its own request with a specific title/body.
• Do not retry a rejected request immediately — a cool-down applies server-side.