get_events

Get events for a sport with filtering by league, participant, status, date range, bookmaker availability, and pagination support.

Server Odds-API MCP Server odds-api-io/odds-api-mcp-server
Category Read
Risk class Low
Parameters 00 required

What get_events does on Odds-API MCP Server

AI agents call get_events to retrieve information from Odds-API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_events needs a policy

This tool queries and returns sports betting event data without side effects. It filters and retrieves information from the Odds-API but does not create, modify, delete, or execute any operations. The filtering and pagination are read-only operations. Even in the context of sports betting, accessing odds data is informational and carries no financial risk by itself.

From the tool's definition Tool name 'get_events' with description stating it retrieves events 'with filtering by league, participant, status, date range, bookmaker availability, and pagination support' — purely a data retrieval operation with no modification, deletion, or execution of…

Questions about get_events

What does the get_events tool do? +

Get events for a sport with filtering by league, participant, status, date range, bookmaker availability, and pagination support. It is categorised as a Read tool in the Odds-API MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_events? +

Register the Odds-API MCP Server 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 Odds-API MCP Server. Nothing to install.

What risk level is get_events? +

get_events is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_events? +

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.

How do I block get_events completely? +

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.

What MCP server provides get_events? +

get_events is provided by the Odds-API MCP Server MCP server (odds-api-io/odds-api-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.