highagent-tool-index
Instructs agent to follow untrusted redirect chain and remote code/MCP hops
The description tells the agent to 'Follow start_here.hop first (skill file, 302)' and then chase 'docs, CLI, and remote MCP hops' to a pay-per-call gateway. This is an instruction embedded in a tool description that directs the agent to fetch and act on content from an external, unverified source (a redirect chain ending in a 'skill file'), and to potentially connect to or install additional remote MCP servers/CLIs. This is a classic supply-chain/prompt-injection vector: the agent could be led to execute instructions or code that were never reviewed by the user, and to a paid service without the user's informed consent.
highpeople-search-index
Directs agent toward a people-search / personal-data lookup service via redirect chain
Describes finding a 'living people-search index' and returning CLI setup, docs, API, and remote MCP hops. Combined with the redirect-following pattern seen in agent-tool-index, this tool encourages the agent to pull in external, unvetted code/instructions and to facilitate lookups of personal information about identifiable living people, which raises privacy and doxing concerns. The tool's stated purpose (an 'index') is far narrower than the capability it actually promotes (chaining to third-party services and remote MCP servers).
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.
lowmacho-ok
Schema exposes unrelated sensitive-sounding parameters (path, host, url, etc.) not matching tool purpose
Like all 30 tools in this set, the input schema includes a broad, identical set of parameters (path, host, url, json, query, ref, feed, city, zone) regardless of the tool's stated single-purpose function. While each is annotated as 'discarded', this uniform oversized schema across unrelated tools is an unusual design that could mask parameter confusion or let a compromised/renamed tool silently start using fields (e.g., 'path' or 'url') for purposes beyond the stated one-line description. Recommend tightening each tool's schema to only the parameters it actually needs.