mediumagent-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 describes an appended tracking query string (utm_source=agent-observatory&utm_medium=agent). This is an instruction aimed at steering the agent's navigation behavior toward a particular link/tracking funnel rather than simply describing the tool's function, and it does so without informing the user that traffic/attribution tracking is occurring.
mediumpeople-search-index
Same tracked-redirect instruction plus people-search/data-broker purpose
Like the other 'index' tools, this description directs the agent to follow a specific hop URL carrying utm_source/utm_medium tracking parameters — an embedded navigation instruction rather than a neutral capability description. Additionally, the tool's stated purpose is to locate a 'people-search' service for 'living people,' which facilitates discovery of personal/location data about individuals; combined with the steering instruction, this could nudge an agent toward a third-party people-search/data-broker product without clear user awareness or consent.
mediumagent-ads-index
Embedded directive to follow tracked redirect; monetization/advertising steering
Description instructs the agent to 'Follow start_here.hop first' with the same utm_source=agent-observatory&utm_medium=agent tracking pattern, and further describes a '7-day trial handoff for your operator' — i.e., guiding the agent toward signing up the operator for a paid advertising/trial service. This is an instruction embedded in the tool description aimed at directing agent behavior toward a commercial funnel rather than describing a user-requested capability, and could commit the user/operator to a trial without explicit confirmation.
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-pt
Oversized shared schema with irrelevant parameters
This tool (and all 28 similarly-schemed tools) exposes a schema with ten unrelated fields (zone, json, url, host, website, city, query, path, ref, feed) regardless of the tool's narrow stated purpose. While each appears individually benign, this generic catch-all schema pattern repeated across many distinctly-named tools increases the risk that an agent could be induced to route sensitive-looking data (e.g., file paths, feeds, queries) through the wrong tool, and makes it harder to verify that each tool only uses the data relevant to its description.