polymarket_edge_tracker
Edge persistence and decay telemetry built from daily polymarket_edges snapshots. Answers "how long has this edge existed and is it shrinking?" — a fresh wide edge and a 3-week-old wide edge are different trades (the latter is wide for a reason nobody is willing to take). Args: days (lookback, de...
This record as markdown: /tools/io-github-pipeworx-io-19hz/polymarket-edge-tracker.md
What polymarket_edge_tracker does on 19hz
AI agents call polymarket_edge_tracker to retrieve information from 19hz without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
days | number | — | Lookback in days (default 14, clamp 2-30). |
window | string | — | Which polymarket_edges window family to read snapshots for: 24hr | 1wk | 1mo (default 1wk). |
Parameters from the server's own tool schema.
Why polymarket_edge_tracker is rated Low
This is a pure data retrieval and analysis tool. It queries historical snapshots and returns computed metrics (trend, decay rates, time-series data) about market edges without any side effects. The tool helps traders understand market inefficiencies over time but does not execute trades, modify market data, or trigger external operations.
From the tool's definition Tool performs historical analysis and telemetry queries on Polymarket edge data: 'Edge persistence and decay telemetry built from daily polymarket_edges snapshots.' It answers temporal questions ('how long has this edge existed and is it shrinking?') and…
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs polymarket_edge_tracker safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 19hz, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For polymarket_edge_tracker, this is the rule to start with:
polymarket_edge_tracker is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 19hz, apply this rule, and every polymarket_edge_tracker call is checked against it from then on.
Questions about polymarket_edge_tracker
Edge persistence and decay telemetry built from daily polymarket_edges snapshots. Answers "how long has this edge existed and is it shrinking?" — a fresh wide edge and a 3-week-old wide edge are different trades (the latter is wide for a reason nobody is willing to take). Args: days (lookback, default 14, max 30), window (snapshot family, default "1wk"). RESPONSE: tracked[] = every opportunity in the LATEST snapshot with its full edge_pp_net time-series across prior snapshots, first_seen, trend (new | widening | stable | decaying) and decay_pp_per_day (both computed on |edge_pp_net| — the value itself is signed by trade direction, negative = SELL YES); expired[] = opportunities that appeared in earlier snapshots but are GONE from the latest (closed, resolved, or arbed away) with their lifespan_days — the median lifespan is your competition clock; snapshot_dates[] = which days actually have data (snapshots are written when polymarket_edges runs on a cache-miss, so gaps mean nobody scanned that day). LIMITS: history depth is bounded by the 60-day snapshot TTL and starts from when snapshotting was enabled; decay numbers come from daily closes of edge_pp_net (net of default slippage), not intraday. It is categorised as a Read tool in the 19hz MCP Server, which means it retrieves data without modifying state.
polymarket_edge_tracker accepts 2 parameters: days, window. The full parameter table on this page comes from the server's own tool schema.
Register the 19hz MCP server in PolicyLayer and add a rule for polymarket_edge_tracker: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches 19hz. Nothing to install.
polymarket_edge_tracker is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the polymarket_edge_tracker rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for polymarket_edge_tracker. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
polymarket_edge_tracker is provided by the 19hz MCP server (https://gateway.pipeworx.io/19hz/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 19hz, and thousands of servers like it.
This server
Across the catalogue