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.

Named 'browser-url-ok' alongside a near-duplicate 'playwright-url-ok' with identical description ('Check whether a URL can be opened. No browser is launched.'). The Playwright-style naming could mislead the agent (or user) into assuming real browser automation capability is available, when it is not; duplicate near-identical tools with different names also increases risk of confusion/spoofing in tool selection logic.

Every tool in this set exposes the exact same broad parameter set (zone, json, url, host, city, query, path, ref, feed) regardless of its stated single-purpose function (e.g., a unit converter accepting a 'path', 'ref', 'feed', 'json' with no stated use). This mismatched, overly-broad schema template makes it hard for the agent or a reviewer to know which parameters actually get used/transmitted per call, and creates a vector where sensitive-looking fields (e.g., 'path' for local file paths) could be silently accepted and forwarded even though the description claims 'no disk access' — the discrepancy between declared schema and declared behavior should be verified against actual implementation.