Repository navigation
fix(mcp): restore "Always allow" for write tools in Claude - #520
Merged
Merged
Conversation
Write tools carried _meta["anthropic/requiresUserInteraction"], which makes Claude drop "Always allow" for the tool. Customers loading BLs and custom fields in bulk had to approve every call (DEV-14831). Remove the key; writes that would lose a value or a party still go through the preview/confirmation flow, and stop/cancel still confirm on every call. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
Contributor
Contributor
Shadow risk calibration
Calibration result: agreement. Shadow risk never blocks or enables merge. Keep it in observation mode until roughly 50 pull requests have human-reviewed labels, then calibrate before considering any policy use. |
alosec
marked this pull request as ready for review
November 18, 2026 00:52
This branch was successfully deployed
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
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.
Fixes DEV-14831: Freight Brokers Global's Claude connector stopped offering Always allow on
track_container,set_custom_field,set_party_roleandupdate_record, so a bulk BL + custom-field load needed one manual approval per call.Cause: the write-safety PRs (#506–#508) added
_meta["anthropic/requiresUserInteraction"]: trueto every tier C tool plustrack_container/resume_shipment_tracking. Claude hides Always allow for tools with that key. Tool annotations (readOnlyHint/destructiveHint) are unchanged from before #506, so this key is the only thing that changed.Fix: stop sending the key, and remove the
requiresUserInteractionregistry flag.What still protects writes:
set_custom_field,set_party_roleorupdate_recordcall that would overwrite or clear a value, or detach a party, still returns a preview and writes only after the user approves it (elicitation or confirmation token).stop_shipment_trackingandcancel_tracking_requeststill confirm on every call.Checks: full MCP suite passes (998/998); the
tools/listsnapshot diff only removes the four_metaentries. Typecheck, eval typecheck and lint are clean. Tests now assert that no tool carries_meta. Docs, README and CHANGELOG updated.After deploy, connected users must click Refresh tools list in Claude's connector settings (or reconnect) to see Always allow again.
🤖 Generated with Claude Code
Open in [code]smith · Need help on this PR? Tag
@codesmith-botwith what you need.