sec: redact absolute file paths from MCP error messages#228
Conversation
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 9 minutes and 52 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (14)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
Prevent Information Disclosure via Error Messages
handleToolError()inpackages/core/src/shared/error-handling.tsreturnserror.messagedirectly to MCP clients. File-not-found errors include full absolute paths (e.g.,/Users/jake/project/custom-elements.json), and Zod validation errors include field names and regex patterns. This leaks project structure information to MCP clients.Implementation
handleToolError()atpackages/core/src/shared/error-handling.ts:Recovered automatically by Automaker post-agent hook