Feature summary (what you would like to be able to do and where):
Allow Edit Filter Managers and Helpers to use proxy information from IP Information tool to be used a conditions, e.g.:

if (ip_behavior == FILE_SHARING) 
  disallow editing

If possible, can one include the details in Behaviors, RIsks, Connection types, Tunnel operator, Proxies from the info tool?

Use case(s) (list the steps that you performed to discover that problem, and describe the actual underlying problem which you want to solve. Do not describe only a solution):

• check if ip address exhibits proxy like behaviours. if yes, disallow ip address from editing on administrative pages.

Benefits (why should this be implemented?):
No open proxies is a global policy, but the enforcement of it is poor due to how dynamic the industry is right now. There are services offering millions of residential IP addresses as proxied IP now, unlike in the past when services largely operates servers running on known/easily discoverable IP addresses.

On enwiki, this was implemented using bots (recently, ST47ProxyBot). However the bot has stopped working due to a disinclination by the operator to continue to run as it is since there are data feeds that we rely on now, as evidently seen on the IP information tool. The bot would also generate millions of the entries in the block log. Currently there have been 13,885,193 blocks from the bot.

Using the edit filter extension to disallow edits from such IP addresses would be an more efficient use of everyone's time. It can also prevent disruptive edits from some users (which enwiki is currently facing on the administrative pages).