List all supported bookmakers with their name and active status.
AI agents call get_bookmakers 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 fetches a static list of bookmaker metadata (names and status). It performs no create, modify, delete, or execute operations. While sports betting data could enable financial decisions, the tool itself only retrieves informational data—users would need to use other tools to place bets or conduct transactions. The blast radius of misuse is minimal; listing bookmakers poses no direct risk.
From the tool's definition Tool name 'get_bookmakers' and description 'List all supported bookmakers with their name and active status' indicate a query operation that retrieves reference data with no side effects.
Attacks that exploit this kind of access
List all supported bookmakers with their name and active status. 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_bookmakers: 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_bookmakers 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_bookmakers 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_bookmakers. 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_bookmakers 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 →