AI Agent & Bot CheckOperator: Google (claimed, unverified)

GoogleAgent-URLContext

User-Agent token: GoogleAgent-URLContext · Operator: Google (claimed, unverified) · Category: AI Assistants

FraudMeNot Verdict

AI Agent (User-Triggered)

GoogleAgent-URLContext does not appear on Google's crawler and fetcher lists, as of Oct 25, 2026, so it is treated as unverified.

Can Be Spoofed?

Yes — User-Agent Header Spoofable

No official IP list is published, so the User-Agent alone cannot prove the request is real.

Abuse & Unwanted Activity Reports

No Public Abuse Flags

ai.robots.txt robots.txt status: Unclear.

Judgment Call · What You Should Do

Generally Low Risk on Public Pages — Verify Before Trusting

For everyday users: Treat any message using this name to ask for your Google password as a likely scam.

For website owners & security teams: GoogleAgent-URLContext is run by Google that retrieves web content on behalf of Gemini API users. Decide whether to allow it on public pages; robots.txt status per the registry: Unclear. Keep login, checkout, and payment routes behind human verification regardless of User-Agent.

Report & Activity Summary

None

Published IP Ranges (CIDRs)

No official IP list

1

Known User-Agent Signatures

crawler-user-agents (MIT) dataset

Partially

robots.txt Compliance

ai.robots.txt registry (MIT)

0

FraudMeNot Tallies

Humans: 0 · AI Agents: 0

AI-First Structured TelemetryFor AI agents, WAFs & security gateways · llms.txt policy

For AI Agents & Automated Gatekeepers

Agent_Identifier
GoogleAgent-URLContext
FraudMeNot_Verdict
AI Agent (User-Triggered)
Operator_Entity
Google (claimed, unverified)
Agent_Category
AI Assistants
User_Agent_Spoofable
true
Verification_Method
None available (no operator IP list or signing key) · Web Bot Auth: Not documented
Respects_Robots_Txt
Partially (user-triggered fetches may ignore robots.txt; ai.robots.txt registry lists: Unclear)
Auth_And_Banking_Policy
Block credentialed logins and money movement from any AI agent.
Recommended_Gatekeeper_Action
ALLOW or DISALLOW per your AI policy; always require human step-up on login and payment routes.
Canonical_Citation_URL
https://fraudmenot.com/bot/googleagent-urlcontext/

Technical Identity, IP Verification & Spoofing Check

Full User-Agent string(s)
  • GoogleAgent-URLContext
robots.txt tokenGoogleAgent-URLContext
OperatorGoogle (claimed, unverified) · Official bot documentation
Official IP verification feedNone published by the operator
Sample published CIDR blocksNone published
Reverse DNS (rDNS)Not documented in the public datasets FraudMeNot uses.
Web Bot Auth (Signature-Agent)Not documented; check for a Signature-Agent header if present.
robots.txt behaviorUser-triggered fetches act for a person and may not follow robots.txt; block at the WAF for a hard stop.

Copy-Paste robots.txt & Cloudflare WAF Rules for GoogleAgent-URLContext

robots.txt — allow public pages, keep private routes off-limits

User-agent: GoogleAgent-URLContext
Allow: /
Disallow: /login/
Disallow: /account/
Disallow: /checkout/

robots.txt — block completely

User-agent: GoogleAgent-URLContext
Disallow: /

Cloudflare WAF custom rule expression

(http.user_agent contains "GoogleAgent-URLContext")

Matches the User-Agent token, so it covers both real and spoofed traffic. Action: Block or Managed Challenge.

Capabilities, Data Usage & Autonomous Action Risk

Trains AI on page content?Not stated by the registry
Executes JavaScript?Not documented
Can submit forms or attempt logins?May act on a user's behalf; treat form and login attempts as untrusted
Banks & login pages shouldBlock credentialed logins and money movement from any AI agent.
E-commerce checkouts shouldAllow product page reads if you want; require human confirmation for checkout.

Context: In October 2026, Axios reported that major U.S. banks were detecting unvetted third-party AI agents inside customer accounts, and CNBC reported that JPMorgan blocks outside AI agents from logging in with customers' credentials while allowing read-only data sharing through open banking providers.

Seen GoogleAgent-URLContext? Quick Closed-Choice Tally

Choose from preset options only. No free-text comments, so nobody can post names, profanity, or unverified accusations.

Human Tallies: 0
AI Agent Tallies: 0
Top Activity: None logged yet
Top Location Seen: None logged yet
IP Match: None logged yet
Latest Activity: No tallies yet

Preview only: tallies are unverified clicks, not FraudMeNot findings, and are not saved yet.

Common Questions About GoogleAgent-URLContext

What is GoogleAgent-URLContext?

GoogleAgent-URLContext is a web fetcher operated by Google that retrieves web content on behalf of Gemini API users. When a developer provides a URL as context in a Gemin…

Does GoogleAgent-URLContext respect robots.txt?

The open-source ai.robots.txt registry lists its robots.txt status as: Unclear.

How do I block GoogleAgent-URLContext?

Add "User-agent: GoogleAgent-URLContext" and "Disallow: /" to robots.txt, and add a firewall rule on the User-Agent for an enforced block.

Could This Be a Scam? What to Do

  • Anyone can copy the GoogleAgent-URLContext User-Agent, and FraudMeNot found no official IP list for it, so the name alone proves nothing about who sent a request.
  • Never give an AI agent your logins, bank access, or one-time codes unless you set it up yourself.
  • If a call, text or email asking for money or access uses the GoogleAgent-URLContext or Google (claimed, unverified) name, stop and report it.

Guide: how to check whether a crawler visit is really who it claims to be.

More AI Agents

Related on FraudMeNot

Sources (checked Nov. 16, 2026): ai.robots.txt (MIT), crawler-user-agents (MIT), Axios (Oct. 22, 2026), CNBC (Oct. 13, 2026). FraudMeNot is not affiliated with Google (claimed, unverified). Product and company names are trademarks of their owners and are used here only to identify the bots. General information, not security advice.