polymarket-predictradar-data-layer-skills

Shared Polymarket and prediction-market data access layer. Use this skill whenever another skill or task needs trader positions, trade history, market metada...

This skill appears to implement the claimed Polymarket/PredicTradar data layer, but several implementation details are inconsistent with the declared metadata and introduce risk: - The code expects/reads environment variables (MCP_URL, MCP_API_KEY) and proxy env vars even though the registry metadata lists no required env. If you set MCP_API_KEY, treat it as a secret and only provide it in a controlled environment. - The skill runs local commands to detect proxies (scutil, python3 via execFileSync). If you run this on a machine where those binaries exist, they will be executed. Consider running in an isolated container if you are concerned. - The gamma-client disables TLS certificate verification (rejectUnauthorized: false) when establishing TLS connections; this weakens transport security and can expose you to man-in-the-middle tampering of gamma-api.polymarket.com interactions. - The skill writes cache files under scripts/cache and includes a warm-up script that performs many queries; expect disk usage and potentially heavy network/API usage. Review and control when/if init.js is run. - The absence of declared env requirements is an inconsistency — ask the publisher (or inspect code) before supplying any credentials or exposing sensitive networks. If you decide to install, run it in a sandboxed environment, avoid supplying sensitive credentials unless necessary, and consider patching the TLS setting (enable certificate verification) and removing or restricting local exec calls if you cannot trust the runtime.

Type: OpenClaw Skill Name: polymarket-predictradar-data-layer-skills Version: 1.0.0 The skill bundle provides a sophisticated data access layer for Polymarket via an MCP server and the Gamma API. It is classified as suspicious due to several high-risk security vulnerabilities: `gamma-client.js` explicitly disables TLS certificate verification (`rejectUnauthorized: false`), which exposes the agent to Man-in-the-Middle (MitM) attacks. Additionally, `proxy-config.js` executes system-level commands (`scutil`) and spawns a `python3` process to detect proxy settings. While these implementations appear to be functional choices for handling network environments without external dependencies, they represent significant security flaws and invasive system interactions.