Well, I am not sure... Maybe it can have 2 parts:
1 - Preventing access of external sites through chrome:// to local resources
2 - Preventing attacks from of external sites related to RSS via trusted chrome://
But maybe some of that is already managed.
I already use below, but not sure if it does apply to chrome://
Site LOCAL
Accept from LOCAL
Deny INC
Accept GET from .getforcastfox.com
Deny
1 - Preventing access of external sites through chrome:// to local resources
2 - Preventing attacks from of external sites related to RSS via trusted chrome://
But maybe some of that is already managed.
I already use below, but not sure if it does apply to chrome://
Site LOCAL
Accept from LOCAL
Deny INC
Accept GET from .getforcastfox.com
Deny