Search events by team name or text query. Returns up to 10 matching results.
AI agents call search_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.
This tool queries and retrieves sports betting event data based on search criteria. It has no side effects, does not modify data, does not execute code, does not delete data, and does not involve financial transactions. It is purely informational data retrieval, matching the Read category definition.
From the tool's definition Tool description states 'Search events...Returns up to 10 matching results' and 'get_events' sibling tool indicates this is a data retrieval operation. No modification, deletion, execution, or financial transaction occurs.
Attacks that exploit this kind of access
Search events by team name or text query. Returns up to 10 matching results. It is categorised as a Read tool in the Odds-API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Odds-API MCP Server MCP server in PolicyLayer and add a rule for search_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.
search_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 search_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 search_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.
search_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.
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 →