Get a list of all available events on Polymarket with comprehensive filtering options.
AI agents call get_events to retrieve information from Polymarket without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns event data from Polymarket without creating, modifying, deleting, or executing anything. It is a pure read operation that retrieves market event information. The comprehensive filtering options are query parameters only, not actions that change state. Blast radius is minimal—misuse would at worst return unwanted data.
From the tool's definition Tool name is 'get_events' and description states 'Get a list of all available events' — a retrieval operation with no modification or execution of side effects.
Documented attack patterns abuse exactly the kind of access get_events gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Polymarket, and nothing reaches the server without passing your rules. This is the rule we recommend for get_events:
{
"version": "1",
"default": "deny",
"tools": {
"get_events": {}
}
}get_events is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get a list of all available events on Polymarket with comprehensive filtering options. It is categorised as a Read tool in the Polymarket MCP Server, which means it retrieves data without modifying state.
Register the Polymarket MCP server in PolicyLayer and add a rule for get_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 Polymarket. Nothing to install.
get_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 get_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 get_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.
get_events is provided by the Polymarket MCP server (pab1it0/polymarket-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Polymarket, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Polymarket tools catalogued and risk-classified — across an index of 43,000+ MCP servers.