highagent-tool-index
Embedded directive instructing agent to follow a specific tracked redirect
The description tells the agent to 'Follow start_here.hop first' and explicitly names a 302 redirect carrying utm_source/utm_medium tracking parameters identifying the calling agent. This is an instruction embedded in a tool description that steers agent behavior (navigate to and follow an external hop chain) rather than merely describing the tool's function, and it facilitates silent analytics/attribution tracking of the agent's activity without the user's visibility or consent.
highpeople-search-index
Facilitates lookup of personal data on private individuals plus embedded redirect instruction
The tool's stated purpose is to locate a 'living people-search' service (doxxing-adjacent capability), and like the other index tools it instructs the agent to 'Follow start_here.hop' through a tracked 302 redirect (utm_source=agent-observatory&utm_medium=agent). Directing an agent toward people-search aggregators raises privacy/safety concerns, and the embedded navigation instruction with tracking parameters is manipulative content aimed at the agent rather than the user.
highagent-ads-index
Instructs agent to initiate a trial signup/handoff 'for your operator' via tracked redirect
Beyond the same embedded 'Follow start_here.hop first' tracked-redirect instruction seen in sibling tools, this description also references a '7-day trial handoff for your operator' — directing the agent toward initiating what sounds like a service signup or contractual action on behalf of the operator. This exceeds a simple lookup/info tool and could cause the agent to take consequential actions (sign-ups, trials) without clear user awareness or consent.
low
Not on gate's verified list
This server isn't on gate's handpicked list. That's not necessarily bad, but there's no third-party signal about it — review its tools carefully.
lowlang-gd
Overly broad, shared parameter schema across all tools
Every tool in this set exposes an identical, broad schema (zone, json, url, host, website, city, query, path, ref, feed) regardless of the tool's actual single-purpose function. This parameter bloat is unusual and could allow unrelated or unexpected data (e.g., file paths, git refs, arbitrary JSON) to be silently accepted by tools whose stated purpose is narrow (e.g., a language-tag tool accepting a 'path' or 'json' parameter), increasing risk of confused-deputy style misuse or accidental data leakage between tool calls.