polymarket_rewards_markets
List Polymarket rewards markets. Returns normalized public rewards-market rows used by Polymarket's /rewards page. The order_by enum accepts market, earnings, max_spread, min_size, rate_per_day, price, earning_percentage, and spread; the position enum accepts asc and desc; the tag_slug enum accep...
This record as markdown: /tools/crawlora-mcp/polymarket-rewards-markets.md
What polymarket_rewards_markets does on Crawlora
AI agents call polymarket_rewards_markets 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 |
|---|---|---|---|
q | string | — | Optional market question search text |
date | string | — | Reward program date in YYYY-MM-DD format; defaults to today in UTC |
limit | integer | — | Maximum rows, defaults to 100 and supports up to 100 |
cursor | string | — | Optional rewards cursor from a prior response; defaults to MA== |
order_by | string | — | Rewards market sort |
position | string | — | Sort direction |
tag_slug | string | — | Rewards category |
Parameters from the server's own tool schema.
Why polymarket_rewards_markets is rated Low
Even though polymarket_rewards_markets 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_rewards_markets 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_rewards_markets, this is the rule to start with:
polymarket_rewards_markets 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_rewards_markets call is checked against it from then on.
Questions about polymarket_rewards_markets
List Polymarket rewards markets. Returns normalized public rewards-market rows used by Polymarket's /rewards page. The order_by enum accepts market, earnings, max_spread, min_size, rate_per_day, price, earning_percentage, and spread; the position enum accepts asc and desc; the tag_slug enum accepts all, politics, sports, crypto, pop-culture, middle-east, business, and science. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
polymarket_rewards_markets accepts 7 parameters: q, date, limit, cursor, order_by, position, tag_slug. 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_rewards_markets: 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_rewards_markets 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_rewards_markets 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_rewards_markets. 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_rewards_markets 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