Details
Why This Is a Vulnerability
The project treats AGENTICMAIL_MASTER_KEY as the authorization boundary for
administrative and gateway operations. HTTP MCP mode removes the client-side
authentication boundary entirely, so an unauthenticated network client becomes
an indirect caller of master-only API functionality.
Suggested Fix
- Require authentication for HTTP MCP mode.
- Bind the MCP HTTP server to
127.0.0.1by default. - Reject
/mcprequests that lack a valid bearer token or shared secret. - Disable master-key tools when the transport is unauthenticated.