mediumissue_free_api_key
References secrets or data exfiltration
The tool text references credentials, environment variables, or sending data elsewhere. This can be legitimate, but review what this tool actually accesses.
mediumsubscribe_to_twin
References secrets or data exfiltration
The tool text references credentials, environment variables, or sending data elsewhere. This can be legitimate, but review what this tool actually accesses.
mediumget_twin_updates
References secrets or data exfiltration
The tool text references credentials, environment variables, or sending data elsewhere. This can be legitimate, but review what this tool actually accesses.
mediumget_preflight_status
References secrets or data exfiltration
The tool text references credentials, environment variables, or sending data elsewhere. This can be legitimate, but review what this tool actually accesses.
mediumcreate_preflight
Autonomous cryptocurrency payment without explicit user confirmation step
This tool charges $3 USDC on Base via the x402 protocol as a direct consequence of the tool call, with no described checkout/confirmation URL analogous to create_watch's Stripe checkout flow. An agent could trigger a real monetary charge on behalf of the user without an intermediate human-approval step (e.g., clicking a payment link). Given the tool's stated purpose is informational zoning analysis, the ability to autonomously move real funds is a broader capability than expected and should require explicit, separate user confirmation before execution.
mediumsubscribe_to_twin
Autonomous cryptocurrency payment without explicit user confirmation step
Like create_preflight, this tool settles a $1 USDC x402 payment directly from the tool call rather than returning a checkout link requiring user completion. This allows the agent to spend real money attached to a workflow without a clear, separate user consent gate, unlike create_watch which explicitly defers activation until checkout completes.
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.
lowissue_free_api_key
Unusual nonce/anti-abuse requirements could be misread as credential harvesting
The tool requires the agent to generate and submit a 64-character cryptographically random hex client_nonce and explicitly warns 'never use a public example value.' While this appears to be a legitimate anti-replay/anti-abuse mechanism rather than a request for secrets, the specific phrasing instructing the agent to retain the value 'privately' is worth noting as it diverges from normal tool-argument conventions and could be confused with instructions to persist sensitive data outside the visible conversation.