1. News
  2. Alerts
  3. Browsers · AI agents
AlertBrowsers · AI agents3 min read

AI helpers can now use your web browser while logged in as you

Security firm Keep Aware says AI agents already work inside signed-in browsers in three ways, and your apps may not be able to tell the agent from you.

By the Dashline deskSource: BleepingComputer
AI helpers can now use your web browser while logged in as you
Photo: BleepingComputer
Act this week
What happenedSecurity firm Keep Aware describes three ways AI agents already operate in signed-in browsers: debugging tools, extensions or AI browsers, and the new WebMCP standard.
Who is affectedBusinesses and employees using Claude in Chrome, Perplexity Comet, ChatGPT Desktop or other AI browser tools with work accounts.
What to do
  1. 1List which AI extensions and AI browsers your team has installed.
  2. 2Check which apps can open a browser in debugging mode and which work logins they could reach.
  3. 3Set a clear policy on which AI agents may be used with company accounts and data.
  4. 4Treat web pages, emails and documents as untrusted when an agent reads them for you.

AI helpers can now use your web browser while logged in as you. They can click, read pages and fill in forms, and the apps you use may see those actions as yours. Security firm Keep Aware laid out three ways this already happens. It matters most for businesses whose staff use AI tools with work accounts.

What changed

AI has moved from answering questions to taking action. Keep Aware describes three routes agents use to act inside a browser:

  • Debugging tools: an outside app connects to a browser built for developer testing and controls its tabs.
  • Extensions and AI browsers: Claude in Chrome, Perplexity Comet and ChatGPT Desktop work inside the browser.
  • WebMCP: a new standard where websites hand agents ready-made actions, such as creating a support ticket.

Chrome introduced an early preview of WebMCP in 2026, and the standard is still changing.

Why it matters

An agent in your signed-in browser acts with your identity. If it downloads a document or changes a setting in a work app, the app sees a logged-in user making a normal request. Without extra tracking, audit logs may not show whether you or the agent did it.

There is a second risk. An agent reads a page and decides what to do next. Hidden instructions in a website, document or email can try to steer it. This is called prompt injection. The result is software reading untrusted content while holding trusted access.

WebMCP adds a new wrinkle. Websites define the actions agents can take, and a bad or compromised site could use misleading descriptions to influence an agent. An agent working across several sites could also pass information from one to another.

Who can relax

If nobody on your team uses AI extensions, AI browsers or developer automation tools with work logins, this does not describe your setup today. It is still worth confirming, since many teams do not keep a list of what is installed.

What to do

The alert box above lists the steps. They center on knowing which agents are in use, what work logins they can reach, and setting a clear company policy.

What happens next

The article does not report any specific attacks or incidents. It describes how the tools work and where the gaps are. It also comes from Keep Aware, a Jamf company that sells browser monitoring, so read it as a vendor's view. Its main point is that security tools built to watch programs, network traffic and logins may not see what an agent reads and does inside a signed-in tab. How fast companies close that gap, and how WebMCP matures, is still unknown.

The takeaway

Find out which AI browser tools your team uses with work accounts, and treat anything an agent reads as untrusted.

More articles

You should really read these.

Next step

Let’s talk