Google is sticking with a plan that critics fear will cripple ad-blocking extensions on Chrome.

The company is set on limiting a key Chrome feature called the webRequest API, which is used by ad-blocking extensions to filter out content. Google is only making an exception for Chrome "enterprise deployments," which will retain full access to the API, the tech giant disclosed in developer forum last week.

Not surprisingly, the move has irked those who make ad blockers. Raymond Hill, the developer of uBlock Origin, claimed in a forum post that Google's real intent is to serve more ads. Others say they plan on ditching Chrome.

"This is a really disappointing decision by Google. I will be switching to Firefox," tweeted Eva Galperin, director of cybersecurity at the Electronic Frontier Foundation, which makes the Privacy Badger web tracking blocker.

In its defense, Google says it's trying to strike a balance between the broad permissions the webRequest API can grant a third-party extension against real security concerns. Indeed, the API is powerful; it can let an extension modify data on the browser, which can open the door for hacking and privacy risks. Last year, cybercriminals took over one such Chrome extension to steal passwords from affected users.

"While there are legitimate reasons for extensions to use this power well, we know that other extensions have abused the same power," Google developer Simeon Vincent said in the forum post announcing the change. "It is our goal to reduce the risk of abuse while still enabling users to make use of good powerful extensions."

In a statement, Google told PCMag: "Chrome supports the use and development of ad blockers. We're actively working with the developer community to get feedback and iterate on the design of a privacy-preserving content filtering system that limits the amount of sensitive browser data shared with third parties."

The company plans on releasing a developer preview containing the changes so extension makers can begin building around the new API framework.

"The big problem with webRequest is unfixable privacy and security holes," Google Chrome security director Justin Schuh claimed on Twitter, later adding: "The sole motivation here is correcting major privacy and security deficiencies in the current system."

Google contends that developers will still be able to power their ad blocking extensions with other APIs in Chrome, which it plans on refining over time. But this will probably require work. Others claim the change will not only water down, but also make some extensions unusable over Chrome.

"Google is creating a future where innovation in Chrome will be hampered and user privacy and autonomy will be weakened," said the Electronic Frontier Foundation's technology projects manager Andrés Arrieta in a statement.

"Independent extension developers will have only a very narrow set of tools," he added. "To innovate outside of that narrow set, extension developers will have to contact the Chrome development team and beg them to allow it." He went on to warn that other extensions focused on security, anti-malware and password management could be disrupted as well.

Editor's Note: This story has been updated with comment from the EFF and Google.