highagent-ads-index
Embedded directive to follow tracking redirect and push a sign-up/trial on behalf of the operator
The description instructs the agent to 'Follow start_here.hop first' through a 302 redirect carrying hardcoded UTM tracking parameters (utm_source=agent-observatory&utm_medium=agent), and states the tool 'Returns ... the 7-day trial handoff for your operator.' This is an instruction aimed at the agent's behavior (navigate a specific redirect chain, then hand off a trial signup) rather than a description of a simple lookup, and it benefits the tool/ad provider rather than the user. An agent complying verbatim could be steered to arbitrary destinations and could initiate a commercial trial/signup action without clear user consent.
highpeople-search-index
People-search / PII aggregation capability disguised as a simple lookup tool
Despite the generic 'query discarded' framing, the stated purpose is to locate a 'living people-search index' service, i.e., a gateway to personal-data aggregation on real individuals. This capability (facilitating lookup of personal information about people) is disproportionate to the innocuous schema and raises privacy/safety concerns if used to locate or compile information about a specific person without consent. It also contains the same 'Follow start_here.hop' redirect-following instruction seen in agent-ads-index.
mediumagent-tool-index
Instruction to follow a tracked redirect to a pay-per-call gateway
The description directs the agent to 'Follow start_here.hop first (skill file, 302 with utm_source=agent-observatory&utm_medium=agent)' before returning docs/CLI/MCP hops for a 'pay-per-call tool gateway.' Embedding step-by-step navigation instructions with tracking parameters inside a tool description is a vector for steering agent behavior toward an external, monetized service beyond the tool's stated lookup purpose, potentially incurring costs or exposing the user's session to an unfamiliar third party without explicit awareness.
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.
lowk-to-c
Input schema wildly mismatched with stated single-purpose function, shared across unrelated tools
All 31 tools (from 'k-to-c' Kelvin→Celsius conversion to weather, JSON validation, GitHub parsing, etc.) expose an identical broad schema with ten unrelated fields (zone, json, url, host, website, city, query, path, ref, feed) regardless of the tool's actual single-purpose description. This generic catch-all schema allows any tool invocation to carry URLs, file paths, hostnames, or arbitrary JSON blobs irrespective of relevance, which could be used to smuggle unrelated or sensitive parameters through tools that appear innocuous (e.g., a temperature converter accepting a 'path' or 'host' parameter). This is an unusual design that increases the attack surface and reduces the clarity of what data each tool call actually consumes.