polymarket_search
Search Polymarket events. Searches Polymarket's credential-free public search JSON and returns normalized event results. The status enum accepts open, closed, and all; the sort enum accepts relevance, volume24hr, volume, liquidity, and endDate.
This record as markdown: /tools/crawlora-mcp/polymarket-search.md
What polymarket_search does on Crawlora
AI agents call polymarket_search 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 | Yes | Search query |
sort | string | — | Search sort |
limit | integer | — | Maximum events, defaults to 10 and supports up to 50 |
status | string | — | Event status filter |
ascending | boolean | — | Sort ascending when true |
include_tags | boolean | — | Include matching tags |
include_profiles | boolean | — | Include matching profiles |
Parameters from the server's own tool schema.
Why polymarket_search is rated Low
Even though polymarket_search 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_search 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_search, this is the rule to start with:
polymarket_search 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_search call is checked against it from then on.
Questions about polymarket_search
Search Polymarket events. Searches Polymarket's credential-free public search JSON and returns normalized event results. The status enum accepts open, closed, and all; the sort enum accepts relevance, volume24hr, volume, liquidity, and endDate. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
polymarket_search accepts 7 parameters: q, sort, limit, status, ascending, include_tags, include_profiles. Required: q. 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_search: 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_search 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_search 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_search. 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_search 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