-
Notifications
You must be signed in to change notification settings - Fork 365
Description
I'm encountering a "Connector is not safe" error when attempting to connect an MCP. The error only occurs when I define a tool with the name "credit-card-providers-tool".
I suspect this is due to some security rule that flags tool names containing sensitive keywords like "credit-card". While I understand the security concerns, this validation seems overly restrictive - it's blocking legitimate use cases where tools need to work with credit card information (like comparing credit card benefits, rewards programs, etc.) without handling actual card numbers or sensitive payment data.
The tool itself doesn't process any sensitive payment information; it only works with publicly available credit card product information.
Suggestion:
Could the security validation be more nuanced? Perhaps allow these tool names with appropriate warnings, or validate based on the tool's actual functionality rather than just keyword matching in names?
