Get the authenticated user
AI agents call get_selected_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 retrieves user account information without modifying, deleting, or executing any external operations. It is a straightforward query operation. Severity is low because exposure of user authentication metadata poses minimal risk compared to financial operations or destructive actions; the blast radius is confined to information disclosure about the requesting user.
From the tool's definition Tool description states 'Get the authenticated user' — a retrieval operation with no side effects. Despite the tool name referencing 'selected_bookmakers,' the description indicates it simply fetches user authentication data.
Attacks that exploit this kind of access
Get the authenticated user. 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_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.
get_selected_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_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.
Set action: deny in the PolicyLayer policy for get_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.
get_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.
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 →