clear_selected_bookmakers · Odds-API MCP Server MCP

WHAT IT DOES

What clear_selected_bookmakers does on Odds-API MCP Server

AI agents use clear_selected_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 clear_selected_bookmakers needs a policy

This tool modifies user account state by removing all selected bookmakers. While 'clear' sounds destructive, this is a reversible configuration change (bookmakers can be re-selected), making it a Write operation. The rate limit of once every 12 hours suggests it has meaningful impact but is not truly irreversible.

From the tool's definition Clear all selected bookmakers for the authenticated user

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

clear_selected_bookmakers Rate-limited

clear_selected_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": {
    "clear_selected_bookmakers": {
      "limits": [
        {
          "counter": "clear_selected_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 clear_selected_bookmakers

What does the clear_selected_bookmakers tool do? +

Clear all selected bookmakers for the authenticated user. Limited to once every 12 hours. 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 clear_selected_bookmakers? +

Register the Odds-API MCP Server MCP server in PolicyLayer and add a rule for clear_selected_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 clear_selected_bookmakers? +

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

Can I rate-limit clear_selected_bookmakers? +

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

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

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