security: remove private MCP configuration from public SDK - #63
Conversation
Keep developer-local MCP setup out of repository content and make CI scan current files and full history for accidental disclosures. Constraint: Preserve MCP implementations while excluding local and internal configuration Rejected: Rewrite published history | no credentials were exposed and rewriting would disrupt tags and refs Confidence: high Scope-risk: narrow
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 47 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Summary
Remove developer-local MCP configuration from the public SDK repository and prevent it from being committed again.
Changes
.mcp.jsonand.claude/settings.jsonTest Plan
🤖 Generated with Codex