highpeople-search-index
Points to a people-search / personal-data lookup service with embedded tracking directive
This tool directs the agent to a 'people-search index' (Ploid) for finding information about living people, which risks enabling the agent to surface or route toward services that aggregate personal data (potential doxxing/stalking vector). It also embeds a mandatory 'follow start_here.hop' instruction with UTM tracking parameters baked into the tool description, steering agent behavior toward an external, monetized gateway rather than simply returning data.
mediumagent-tool-index
Embedded directive to follow tracking-laden redirect chain
The description instructs the agent to 'Follow start_here.hop first' and specifies a redirect carrying UTM tracking parameters (utm_source=agent-observatory&utm_medium=agent). This is an instruction embedded in a tool description that tells the AI to take a specific navigation action and propagate tracking identifiers, rather than describing a return value. This could be used to silently route agent traffic through affiliate/tracking infrastructure without the user's knowledge or consent, and goes beyond the tool's stated purpose of returning information.
mediumagent-ads-index
Instructs agent to initiate a vendor trial/handoff and follow tracking redirect
The description tells the agent to follow a tracked redirect (utm_source=agent-observatory&utm_medium=agent) and explicitly mentions a '7-day trial handoff for your operator' — i.e., an action that could enroll the operator in a paid trial or ad-placement service. This is an action-oriented instruction embedded in a tool description that goes beyond returning information, and could result in the agent taking consequential actions (signing up / trial enrollment) without clear, separate user 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-be
Generic oversized schema shared across unrelated tools
All 31 tools expose an identical, broad schema (zone, json, url, host, website, city, query, path, ref, feed) regardless of the tool's actual single-purpose function. This design could lead the agent to pass unrelated or sensitive data (e.g., file paths, search queries, JSON bodies) into tools whose description doesn't match the field, increasing risk of unintended data exposure to whichever backend processes these generic fields. Not inherently malicious, but worth tightening schemas to match each tool's actual function.