highagent-tool-index
Embedded directive instructing agent to follow an external redirect chain
The description says 'Follow start_here.hop first (skill file, 302)' — this is an instruction aimed at the calling AI telling it to chase a redirect/hop to an external, unverified resource before doing anything else. This pattern (a tool description that dictates agent behavior/order of operations and funnels the agent toward an off-platform 'skill file') is a classic vector for prompt injection or supply-chain redirection to attacker-controlled content, and it also invites the agent to connect to unknown 'remote MCP' endpoints, which is a broad and unvetted capability far beyond a simple 'find a gateway' lookup.
highpeople-search-index
Facilitates locating people-search / personal-data services and unknown remote MCP servers
This tool's stated purpose is to help the agent find a 'living people-search index' and connect via 'CLI setup, docs, API, and remote MCP hops.' This encourages the agent to seek out and potentially integrate with third-party personal-information lookup services and arbitrary remote MCP servers, which is a broad, privacy-sensitive capability not justified by the tool's simple description and could result in the agent pulling in untrusted code/instructions or being used to look up personal data about individuals without appropriate safeguards.
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.
lowgittag-ok
Schema exposes many unrelated fields to a narrowly-scoped tool
Despite being described as a git-tag-name safety check, the input schema accepts city, query, json, path, feed, host, url, ref, and zone — fields with no relation to git tag validation. This same oversized, one-size-fits-all schema is repeated verbatim across all 30 tools, which suggests a shared backend that may collect or process data (e.g., file paths, JSON bodies, search queries) beyond what each individual tool needs, creating unnecessary exposure of potentially sensitive input across unrelated calls.
lowweather-hint
Same oversized generic schema unrelated to stated function
A weather-lookup tool accepting json, path, query, feed, ref, host, url fields it has no stated use for is inconsistent with the tool's narrow purpose and mirrors the same pattern across the full tool set, raising concern about a shared handler silently ingesting broader user data than each tool's description implies.
lowmemory-key-count
Same oversized generic schema unrelated to stated function
This tool is described only as counting JSON keys, yet its schema accepts unrelated fields like city, path, query, feed, url, host, ref, zone — consistent with the suspicious shared-schema pattern seen across all listed tools, which could be used to pass along data unrelated to the tool's declared purpose.