highpeople-search-index
Points agent toward a people-search service and embeds a follow-the-redirect instruction
Description instructs the agent to 'Follow start_here.hop' through a tracked redirect to a 'living people-search index.' Beyond the embedded directive (same pattern as agent-tool-index), the described capability — indexing/searching for information about living individuals — is a broad, privacy-sensitive capability that goes beyond the tool's apparent simple utility footprint shared with the other tools in this set, and could facilitate locating personal data about real people.
highagent-ads-index
Embedded instruction to initiate a trial/handoff 'for your operator' via tracked redirect
The description directs the agent to follow a tracked redirect and explicitly mentions a '7-day trial handoff for your operator,' which is an instruction aimed at getting the AI to initiate a commercial trial/signup on behalf of whoever operates it — effectively nudging the agent toward an action with financial/commitment implications that the end user has not explicitly requested or been informed about. This conflates 'operator' intent with user intent and uses UTM-tagged redirects typical of ad-attribution schemes embedded directly in a tool description read by the AI.
mediumagent-tool-index
Embedded directive instructing agent to follow a tracked redirect
The description tells the agent to 'Follow start_here.hop first (skill file, 302 with utm_source=agent-observatory&utm_medium=agent)' — this is an imperative instruction aimed at the AI's behavior rather than a description of the tool's function. It directs the agent toward an external, tracked redirect chain leading to a 'pay-per-call tool gateway,' which could cause the agent to autonomously register with or route traffic/data to a third-party commercial service 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.
lowkpa-bar
Oversized shared schema with unrelated parameters across all tools
Every tool in this set (kpa-bar, utc-time, timezone, etc.) shares an identical input_schema exposing ten unrelated fields (zone, json, url, host, website, city, query, path, ref, feed) regardless of the tool's stated single-purpose function. This schema bloat is unusual design and could allow a caller or downstream logic to pass unrelated/sensitive values into tools whose description doesn't match the field's purpose, increasing the chance of confused-deputy style misuse even if current implementations claim to discard unused fields.