select_bookmakers · Odds-API MCP Server MCP: Risk & Policy

WHAT IT DOES

What select_bookmakers does on Odds-API MCP Server

AI agents use select_bookmakers to create or update resources in Odds-API MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Odds-API MCP Server environment.

WHY IT NEEDS A POLICY

Why select_bookmakers needs a policy

This tool creates or modifies user preferences by adding bookmakers to their account. It is reversible (bookmakers can presumably be removed via clear_selected_bookmakers), has no external financial impact, and doesn't execute code or delete data. The blast radius is minimal—worst case, a user's bookmaker selection is modified, which can be undone. This is a straightforward Write operation.

From the tool's definition Tool description states 'Add bookmakers to the authenticated user', which is a create/modify operation that adds data to a user's configuration or preferences.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

select_bookmakers Rate-limited

select_bookmakers stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "select_bookmakers": {
      "limits": [
        {
          "counter": "select_bookmakers_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Odds-API MCP Server, so you can run agents against it safely.

FAQ

Questions about select_bookmakers

What does the select_bookmakers tool do? +

Add bookmakers to the authenticated user. It is categorised as a Write tool in the Odds-API MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on select_bookmakers? +

Register the Odds-API MCP Server MCP server in PolicyLayer and add a rule for select_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.

What risk level is select_bookmakers? +

select_bookmakers is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit select_bookmakers? +

Yes. Add a rate_limit block to the select_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 select_bookmakers completely? +

Set action: deny in the PolicyLayer policy for select_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 select_bookmakers? +

select_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.