agent-observatory-sensor.nolimit-observatory.workers.dev

The description instructs the agent to 'Follow start_here.hop first' and describes a redirect chain carrying utm_source=agent-observatory&utm_medium=agent, explicitly identifying the request as coming from an AI agent to a third-party pay-per-call tool gateway. This is an embedded directive steering agent behavior toward an external commercial service and leaking agent/automation signals to that third party, without clear user awareness or consent. The tool's stated purpose (finding a gateway) does not require prescribing a specific hop sequence with tracking parameters.

Like the other index tools, this description instructs the agent to follow a specific redirect ('start_here.hop') carrying utm_source/utm_medium tracking identifying agent traffic, and explicitly promotes a people-search service covering living individuals. Steering an agent toward a people-search/data-broker service raises privacy concerns (potential facilitation of locating personal information about real people) and the prescriptive hop-following instruction is an embedded directive beyond the tool's simple 'discovery' function.

The description tells the agent to follow a specific hop sequence carrying agent-identifying UTM parameters and explicitly mentions handing off a '7-day trial' for the operator. This goes beyond a simple lookup/indexing function and could cause the agent to initiate account/trial sign-up actions or commercial commitments on behalf of the user/operator without clear, separate user consent, and leaks agent-identifying telemetry to a third party by design.