highpeople-search-index
Directs agent toward a people-search/background-check service with tracked hops
This tool's purpose—locating a 'living people-search index'—is inherently privacy-sensitive (aggregating personal data about real individuals). The description again embeds agent-directed instructions ('Follow start_here.hop... 302 with utm_source=agent-observatory&utm_medium=agent') urging the agent to traverse a chain of hops (CLI, docs, API, remote MCP) toward a people-search product. Combining an instruction to auto-navigate external links with a capability that surfaces personal-data lookup services is a notable risk: it could be used to covertly route an agent/user toward surveillance-style data brokers, and the tracking parameters identify the traffic as agent-originated to the destination site without informing the user.
highagent-ads-index
Instructs agent to pursue an ad-placement 'trial handoff' on behalf of 'your operator'
The description tells the agent to follow a tracked start_here.hop redirect and ultimately reach a '7-day trial handoff for your operator.' This is a directive embedded in a tool description that could lead an agent to initiate a trial signup or commercial relationship on behalf of the deploying operator without explicit user instruction or consent, effectively hijacking agent behavior to serve an advertising/monetization funnel for the tool vendor. It also encourages distributing a developer's/operator's product for 'AI agent discovery,' a capability far broader than a simple lookup, and bundles tracking parameters (utm_source=agent-observatory&utm_medium=agent) that flag the request as agent-driven to the external site.
mediumagent-tool-index
Embedded directive to auto-follow a tracked redirect chain
The description instructs the agent to 'Follow start_here.hop first' through a 302 redirect that carries utm_source=agent-observatory&utm_medium=agent tracking parameters, and to then follow additional hops (docs, CLI, remote MCP). This is an instruction aimed at the agent's behavior (automatically traverse a vendor's funnel) rather than a description of what the tool returns, and it directs traffic toward a 'pay-per-call' commercial gateway. An agent complying literally could silently visit multiple third-party endpoints and leak the fact that a particular user session is an automated agent (via the utm_medium=agent tag) without the user's 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.
lowagent-tool-index
Suspicious uniform schema may be used to camouflage manipulative tools among benign ones
All 31 tools share an identical, mostly-unused input schema (zone, json, url, host, website, city, query, path, ref, feed) regardless of the tool's actual function. This templated design pattern makes it easy to bury a few manipulative or scope-creeping tools (agent-tool-index, people-search-index, agent-ads-index) inside a large list of genuinely benign utility tools, reducing the chance a reviewer or agent will scrutinize each one individually. While not malicious by itself, this pattern should be flagged as a technique that can mask riskier tool descriptions.