fix: require confirmation before sending email - #55
Open
lizuyi-6 wants to merge 1 commit into
Open
Conversation
Mark email send tools as destructive and require fresh user confirmation before every send or retry to prevent accidental duplicate delivery.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
An interrupted or ambiguous response does not prove that Postmark rejected a send. Automatically retrying can therefore deliver duplicate transactional or OTP emails. The tool metadata and descriptions now tell both MCP clients and models to treat each send attempt as an irreversible action requiring explicit user approval.
Test plan
npm test(34 tests)npm run test:offline(complete offline MCP integration suite)node --check index.jsCloses #54