polymarket_predictions
List Polymarket predictions. Returns normalized event rows for the Polymarket /predictions page using credential-free Gamma events/keyset JSON. The status enum accepts active, resolved, and all; the sort enum accepts competitive, volume, volume_24hr, ending_soon, liquidity, newest, and closed_tim...
This record as markdown: /tools/crawlora-mcp/polymarket-predictions.md
What polymarket_predictions does on Crawlora
AI agents call polymarket_predictions to retrieve information from Crawlora 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 |
|---|---|---|---|
tag | string | — | Optional tag slug |
sort | string | — | Prediction sort |
limit | integer | — | Maximum events, defaults to 20 and supports up to 100 |
cursor | string | — | Optional keyset cursor from a prior predictions response |
status | string | — | Prediction status |
recurrence | string | — | Optional recurrence filter |
Parameters from the server's own tool schema.
Why polymarket_predictions is rated Low
Even though polymarket_predictions only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs polymarket_predictions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crawlora, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For polymarket_predictions, this is the rule to start with:
polymarket_predictions 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 Crawlora, apply this rule, and every polymarket_predictions call is checked against it from then on.
Questions about polymarket_predictions
List Polymarket predictions. Returns normalized event rows for the Polymarket /predictions page using credential-free Gamma events/keyset JSON. The status enum accepts active, resolved, and all; the sort enum accepts competitive, volume, volume_24hr, ending_soon, liquidity, newest, and closed_time; the recurrence enum accepts hourly, daily, weekly, monthly, and yearly. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
polymarket_predictions accepts 6 parameters: tag, sort, limit, cursor, status, recurrence. The full parameter table on this page comes from the server's own tool schema.
Register the Crawlora MCP server in PolicyLayer and add a rule for polymarket_predictions: 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 Crawlora. Nothing to install.
polymarket_predictions 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_predictions 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_predictions. 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_predictions is provided by the Crawlora MCP server (crawlora-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crawlora, and thousands of servers like it.
This server
Across the catalogue