polymarket_events
List live Polymarket events, ranked by volume. An event groups several related markets — use it to discover a topic, then polymarket_markets to price it. Returns title, description, start and end dates, and URL.
This record as markdown: /tools/io-github-getgapup-mcp-knowledge/polymarket-events.md
What polymarket_events does on Mcp Knowledge
AI agents call polymarket_events to retrieve information from Mcp Knowledge 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 |
|---|---|---|---|
async | boolean | — | If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti |
limit | integer | — | Maximum events (default 20) |
includeClosed | boolean | — | Include finished events (default false) |
Parameters from the server's own tool schema.
Why polymarket_events is rated Low
Read-only retrieval of public prediction market event listings with no side effects.
From the tool's definition List live Polymarket events, ranked by volume
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 Mcp Knowledge, 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 Mcp Knowledge, apply this rule, and every polymarket_events call is checked against it from then on.
Questions about polymarket_events
List live Polymarket events, ranked by volume. An event groups several related markets — use it to discover a topic, then polymarket_markets to price it. Returns title, description, start and end dates, and URL. It is categorised as a Read tool in the Mcp Knowledge MCP Server, which means it retrieves data without modifying state.
polymarket_events accepts 3 parameters: async, limit, includeClosed. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Knowledge 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 Mcp Knowledge. 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 Mcp Knowledge MCP server (https://mcp.gapup.io). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Knowledge, and thousands of servers like it.
This server
Across the catalogue