list_bookmakers

List the bookmakers available on your tier. Returns the curated catalogue (each with key, name and class = "sharp" | "asian") plus a note on tier coverage. Free tier excludes the sharp book (Pinnacle). Use the returned key values in the bookmakers filter of get_match_odds / compare_lines.

SERVERInfersports SOURCEhttps://api.infersports.dev/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/dev-infersports-infersports/list-bookmakers.md

WHAT IT DOES

What list_bookmakers does on Infersports

AI agents call list_bookmakers to retrieve information from Infersports without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_bookmakers is rated Low

This tool retrieves and queries information about available bookmakers and their metadata (key, name, class, tier coverage). It has no side effects, does not modify data, and serves a purely informational purpose. It fits squarely within the Read category as a data retrieval operation.

From the tool's definition Tool description states it "List[s] the bookmakers available" and "Returns the curated catalogue". The server description emphasizes "Read-only" access. No modification, deletion, or execution of operations occurs.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_bookmakers safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Infersports, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_bookmakers, this is the rule to start with:

list_bookmakers Allowed

list_bookmakers is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_bookmakers": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Infersports, apply this rule, and every list_bookmakers call is checked against it from then on.

FAQ

Questions about list_bookmakers

What does the list_bookmakers tool do? +

How do I enforce a policy on list_bookmakers? +

Register the Infersports MCP server in PolicyLayer and add a rule for list_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 Infersports. Nothing to install.

What risk level is list_bookmakers? +

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

Can I rate-limit list_bookmakers? +

Yes. Add a rate_limit block to the list_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.

How do I block list_bookmakers completely? +

Set action: deny in the PolicyLayer policy for list_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.

What MCP server provides list_bookmakers? +

list_bookmakers is provided by the Infersports MCP server (https://api.infersports.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Infersports, and thousands of servers like it.

This server

All 17 Infersports tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →