get_match_data
Fetch full context for one Front of Goal event page: teams, kickoff, venue, referee, form, and every market with live odds and CLOB token IDs. Find event_slug via list_upcoming_matches or a frontofgoal.com/event/ URL.
This record as markdown: /tools/com-frontofgoal-odds-api/get-match-data.md
What get_match_data does on Odds Api
AI agents call get_match_data to retrieve information from Odds Api without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
event_slug | string | Yes | The slug from a frontofgoal.com/event/{slug}/ URL |
Parameters from the server's own tool schema.
Why get_match_data is rated Low
Even though get_match_data only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs get_match_data safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Odds Api, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_match_data, this is the rule to start with:
get_match_data is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Odds Api, apply this rule, and every get_match_data call is checked against it from then on.
Questions about get_match_data
Fetch full context for one Front of Goal event page: teams, kickoff, venue, referee, form, and every market with live odds and CLOB token IDs. Find event_slug via list_upcoming_matches or a frontofgoal.com/event/ URL. It is categorised as a Read tool in the Odds Api MCP Server, which means it retrieves data without modifying state.
get_match_data accepts 1 parameter: event_slug. Required: event_slug. The full parameter table on this page comes from the server's own tool schema.
Register the Odds Api MCP server in PolicyLayer and add a rule for get_match_data: 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. Nothing to install.
get_match_data 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_match_data 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_match_data. 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_match_data is provided by the Odds Api MCP server (https://api.frontofgoal.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Odds Api, and thousands of servers like it.
This server
Across the catalogue