Get teams/participants for a sport, optionally filtered by name search.
AI agents call get_participants 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 and queries participant/team data from a sports betting odds API. It performs a search or lookup operation with no side effects—it does not create, modify, delete, execute code, or involve financial transactions. This is a straightforward Read operation with low blast radius if misused by an AI agent.
From the tool's definition Tool name 'get_participants' and description 'Get teams/participants for a sport, optionally filtered by name search' indicate data retrieval with optional filtering. No modification, deletion, execution, or financial operations are described.
Attacks that exploit this kind of access
Get teams/participants for a sport, optionally filtered by name search. 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_participants: 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_participants 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_participants 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_participants. 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_participants 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 →