odds_get_historical_events
Get historical events for a sport at a specific date. Returns events that were available at that point in time.
This record as markdown: /tools/io-github-lacausecrypto-sports-hub/odds-get-historical-events.md
What odds_get_historical_events does on Sports Hub
AI agents call odds_get_historical_events to retrieve information from Sports Hub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why odds_get_historical_events is rated Low
This tool retrieves historical sports betting/odds events data. The verb 'Get' and the passive construction 'Returns events' confirm it performs a read-only query operation. There are no side effects, no data modification, and no external actions triggered. The low severity reflects minimal risk even if misused—returning historical event data poses no financial, destructive, or execution risks.
From the tool's definition Tool name 'odds_get_historical_events' and description 'Get historical events for a sport at a specific date. Returns events that were available at that point in time' indicate pure data retrieval with no modification, creation, or deletion of data.
Attacks that exploit this kind of access
The rule that runs odds_get_historical_events safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sports Hub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For odds_get_historical_events, this is the rule to start with:
odds_get_historical_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 Sports Hub, apply this rule, and every odds_get_historical_events call is checked against it from then on.
Questions about odds_get_historical_events
Get historical events for a sport at a specific date. Returns events that were available at that point in time. It is categorised as a Read tool in the Sports Hub MCP Server, which means it retrieves data without modifying state.
Register the Sports Hub MCP server in PolicyLayer and add a rule for odds_get_historical_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 Sports Hub. Nothing to install.
odds_get_historical_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 odds_get_historical_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 odds_get_historical_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.
odds_get_historical_events is provided by the Sports Hub MCP server (mcp-sports-hub). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sports Hub, and thousands of servers like it.
This server
Across the catalogue