polymarket_events
List Polymarket events. Returns normalized event rows from Polymarket's credential-free public Gamma events JSON.
This record as markdown: /tools/crawlora-mcp/polymarket-events.md
What polymarket_events does on Crawlora
AI agents call polymarket_events 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 |
|---|---|---|---|
limit | integer | — | Maximum events, defaults to 25 and supports up to 100 |
order | string | — | Sort field |
closed | string | — | Closed filter |
offset | integer | — | Result offset, defaults to 0 and supports up to 10000 |
ascending | boolean | — | Sort ascending when true |
Parameters from the server's own tool schema.
Why polymarket_events is rated Low
Even though polymarket_events 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_events 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_events, this is the rule to start with:
polymarket_events 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_events call is checked against it from then on.
Questions about polymarket_events
List Polymarket events. Returns normalized event rows from Polymarket's credential-free public Gamma events JSON. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
polymarket_events accepts 5 parameters: limit, order, closed, offset, ascending. 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_events: 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_events 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_events 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_events. 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_events 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