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...
AI agents call polymarket_edge_tracker to retrieve information from Expression Atlas without modifying anything — 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.
The tool retrieves and analyzes historical snapshot data about Polymarket prediction market edges, computing trends and decay metrics. It is fundamentally a read/query operation over stored telemetry data. However, it is closely tied to financial trading decisions on prediction markets (informing whether to take a trade), making misuse potentially financially impactful.
From the tool's definition Edge persistence and decay telemetry built from daily polymarket_edges snapshots. Answers 'how long has this edge existed and is it shrinking?' — RESPONSE: tracked[] = every opportunity in the LATEST snapshot with its full edge_pp_net time-series
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
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 Expression Atlas 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 Expression Atlas 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 Expression Atlas. 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 Expression Atlas MCP server (https://gateway.pipeworx.io/expression-atlas/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →