Skip to content

fix(mcp): restore "Always allow" for write tools in Claude - #520

Merged
alosec merged 1 commit into
mainfrom
alex/dev-14831-restore-always-allow
Nov 18, 2026
Merged

alosec merged 1 commit into
mainfrom
alex/dev-14831-restore-always-allow

Conversation

@alosec

@alosec alosec commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

Fixes DEV-14831: Freight Brokers Global's Claude connector stopped offering Always allow on track_container, set_custom_field, set_party_role and update_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"]: true to every tier C tool plus track_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 requiresUserInteraction registry flag.

What still protects writes:

  • A set_custom_field, set_party_role or update_record call 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_tracking and cancel_tracking_request still confirm on every call.
  • Additive writes (new tracking, filling empty fields) run at once, which is what the bulk workflow needs.
  • Users who want a prompt per call can still pick "Needs approval" in Claude.

Checks: full MCP suite passes (998/998); the tools/list snapshot diff only removes the four _meta entries. 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


Run Proof
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.

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>
@vercel

vercel Bot commented Nov 18, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
api Ready Ready Preview Nov 18, 2026 12:49am UTC

Request Review

@mintlify

mintlify Bot commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
terminal49 🟢 Ready View Preview Nov 18, 2026, 12:49 AM

💡 Tip: Enable Automations to automatically generate PRs for you.

@linear-code

linear-code Bot commented Nov 18, 2026

Copy link
Copy Markdown
Contributor

DEV-14831

@github-actions github-actions Bot added the risk-shadow:high Shadow-only risk signal: high label Nov 18, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Shadow risk calibration

Signal Result Authority
Path classifier risk:high Deterministic advisory policy
heuristic fallback risk-shadow:high Shadow only

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.

@github-actions github-actions Bot added the risk:unknown Advisory evidence unavailable or changed; no merge permission label Nov 18, 2026
@github-actions github-actions Bot added risk:high Advisory path risk; current-head human review needed and removed risk:unknown Advisory evidence unavailable or changed; no merge permission labels Nov 18, 2026
@alosec
alosec marked this pull request as ready for review November 18, 2026 00:52
@alosec
alosec merged commit 5e7b7c2 into main Nov 18, 2026
32 of 33 checks passed
@alosec
alosec deleted the alex/dev-14831-restore-always-allow branch November 18, 2026 00:52
@github-actions github-actions Bot added risk:unknown Advisory evidence unavailable or changed; no merge permission and removed risk:high Advisory path risk; current-head human review needed labels Nov 18, 2026

This branch was successfully deployed

2 active deployments
Preview — c90b8b12 Deployed Nov 18, 2026 by vercel[bot]
staging - docs — c90b8b12 Deployed Nov 18, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

risk:unknown Advisory evidence unavailable or changed; no merge permission risk-shadow:high Shadow-only risk signal: high

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant