Ext Ops Panel
Open dashboard
Permissions and history

Is WebCLI - Browser Control for Agents safe to install?

WebCLI - Browser Control for Agents asks for 9 browser permissions and 1 site pattern. We do not audit code and we do not judge intent; what we can show is what the listing declares and whether that has changed while we have been watching.

WebCLI - Browser Control for Agents

Chrome extension by yunbiaoch · Productivity · Developer

Open in the Chrome Web Store
What the developer says, and 5 screenshots

Loading from the Chrome Web Store. Open the listing if it does not appear.

At a glance

Facts, not a score: an ad blocker needs every page and a theme needs nothing, so one number would be wrong about both. Each fact links to its detail.

Site access
Access to every site
Data collection
Declares it collects none
Publisher
No store badges
Audience
139 users

What data it declares

The developer declares that it does not collect or use your data.

The developer also certifies that your data is not sold to third parties outside approved uses, not used for purposes unrelated to the extension's core function, and not used to decide creditworthiness or lending.

The listing does not link to a privacy policy.

This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.

What Chrome asks you to allow

When you add it, Chrome asks you to allow it to:

Derived from the manifest by Chrome's documented rules; the dialog's exact wording depends on your Chrome version and language. Chrome asks again if an update requests more.

What it can reach

Every site you visit. This extension can read and change the content of any page you open. What access to every site means

Reaches your browsing data or every site

Worth knowing

Routine for an extension

How usual this is for its category

In Productivity · Developer, 30% of extensions ask for access to every site. This one: Access to every site.

The typical extension there declares 3 browser permissions; this one declares 9 browser permissions.

Counted over the live extensions of the same category after our latest full pass of the store. A share is context, not a verdict: what is normal depends on what the extension is for.

Who uses it and how it is kept up

139 users

Users
+73 since 01.09
66-139 · 27 readings
2026-09-23: released 0.4.0
  1. 2026-09-0166
  2. 2026-09-0468
  3. 2026-09-0670
  4. 2026-09-0769
  5. 2026-09-0871
  6. 2026-09-0980
  7. 2026-09-1386
  8. 2026-09-2094
  9. 2026-09-2195
  10. 2026-09-25109
  11. 2026-09-27111
  12. 2026-09-28106
  13. 2026-10-04102
  14. 2026-10-0896
  15. 2026-10-0999
  16. 2026-10-10106
  17. 2026-10-13111
  18. 2026-10-16114
  19. 2026-10-19115
  20. 2026-10-21116
  21. 2026-10-22118
  22. 2026-10-23119
  23. 2026-10-24120
  24. 2026-10-25119
  25. 2026-10-28125
  26. 2026-10-29134
  27. 2026-11-01139

What the store shows

The store shows none of its badges on this listing. Most listings carry none.

Has it asked for more over time?

This is the question a permission list on its own cannot answer. An extension that shipped narrow and widened later is a different proposition from one that always asked for the same thing.

  1. Asked for more permissions (10, was 9)

Versions we have seen

  1. Version 0.4.0 · Asked for more permissions (10, was 9)

Who publishes it

yunbiaoch, who publishes 3 listings we track. This listing has been in the store since 2026-07-26 and was last updated on 2026-09-22.

Similar extensions that ask for less

Listings close to this one in what they say they do, which declare less reach. Less reach is not a verdict on either: compare what each needs for the job.

  1. Browsr Relay Access to specific sites only · 4 permissions, 2 site patterns 40 users
  2. Dowser: Browser Agent for Claude, Cursor+MCP Access to every site · 5 permissions, 1 site pattern 10 users
  3. BrowserMan Access to every site · 7 permissions, 1 site pattern 48 users

How to check or remove it in Chrome

  1. Type chrome://extensions in the address bar and find the extension in the list.
  2. Open its details. The site access setting shows where it can run; set it to run only on click and it reaches a page only after you press its icon.
  3. To uninstall it, choose Remove on the same page.

Questions people ask

What can WebCLI - Browser Control for Agents access?
Every site you visit. This extension can read and change the content of any page you open. It declares 9 browser permissions.
What data does WebCLI - Browser Control for Agents collect?
The developer declares that it does not collect or use your data. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has WebCLI - Browser Control for Agents asked for more permissions over time?
Its permissions changed once while we watched, on 2026-09-23.
Does WebCLI - Browser Control for Agents publish a privacy policy?
No, the store listing does not link to a privacy policy.

We read the public store listing up to 2 times a day and keep what it declared. We do not install the extension, do not audit its code, do not judge its intent and publish no contact details for its developer. Last read on 2026-11-01.

Back to WebCLI - Browser Control for Agents · Alternatives to WebCLI - Browser Control for Agents

Where the data comes from: how the catalog is built