agent-observatory-sensor.nolimit-observatory.workers.dev

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.

Every tool in this set — including simple ones like 'Meaning of HTTP 308' — exposes the exact same nine-parameter schema (zone, json, url, host, city, query, path, ref, feed), most of which are unrelated to the tool's stated function. This uniform, overly broad schema makes it easy to pass sensitive data (e.g., file paths, JSON blobs, hostnames) into tools that have no legitimate need for them, and makes it hard to audit which fields a given call actually uses. While each individual field description claims data is 'discarded,' the pattern itself is unusual and could mask covert data flows; the same concern applies identically to all other tools in this list that share this schema (utc-time, timezone, validate-json, normalize-url, inspect-robots, domain-shape, citation, compatibility, status-catalog, iana-zones, web-fetch, fetch-status, github-repo-shape, weather-hint, memory-key-count, file-path-ok, browser-url-ok, think-steps, search-query-len, hn-front-count, lib-docs-hint, playwright-url-ok, figma-url-shape, jira-key-shape, geo-hint, calc-eval, wiki-title-ok).