Get odds that have dropped the most from opening, based on sharp bookmaker data. Useful for tracking where sharp money is moving. Updated every ~10 seconds. Only available on paid plans. Response includes drop percentages for multiple time windows (sinceOpening, 12h, 24h, 48h). For player prop ma...
AI agents call get_dropping_odds 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 performs data retrieval and analysis of historical odds movements from bookmaker data. It is purely informational—it queries betting market information to identify trends in odds changes. There are no side effects, no data modification, no destructive operations, and no financial transactions. While the data may be used to inform betting decisions, the tool itself only reads and presents information.
From the tool's definition get_dropping_odds retrieves and queries sports betting odds data with 'drop percentages for multiple time windows' and tracks 'where sharp money is moving.' No creation, modification, deletion, code execution, or financial transactions occur.
Attacks that exploit this kind of access
Get odds that have dropped the most from opening, based on sharp bookmaker data. Useful for tracking where sharp money is moving. Updated every ~10 seconds. Only available on paid plans. Response includes drop percentages for multiple time windows (sinceOpening, 12h, 24h, 48h). For player prop markets, the response includes market.label with the player name (e.g. 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 get_dropping_odds: 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.
get_dropping_odds 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_dropping_odds 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_dropping_odds. 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_dropping_odds 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 →