Get football / soccer match results / scores and fixtures for a league and season (e.g. Bundesliga). Optionally narrow to a single matchday. Returns teams, kickoff datetime, final score, and whether each match is finished.
AI agents call get_matches to retrieve information from Mcp Openligadb without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
league | string | Yes | League shortcut, e.g. 'bl1' (Bundesliga), 'bl2' (2. Bundesliga), 'bl3' (3. Liga), 'dfb' (DFB-Pokal). |
season | string | Yes | Season start year, e.g. "2024". |
matchday | number | — | Optional matchday number (1-based). |
Parameters from the server's own tool schema.
This is a pure data retrieval operation querying OpenLigaDB for historical and scheduled match information. It has no side effects, cannot modify data, execute code, delete records, or affect financial systems. The read-only nature and non-sensitive sports data context justify low severity.
From the tool's definition Tool retrieves match results, scores, and fixtures with 'Returns teams, kickoff datetime, final score, and whether each match is finished.' No modification, deletion, or execution of external systems occurs.
Attacks that exploit this kind of access
Get football / soccer match results / scores and fixtures for a league and season (e.g. Bundesliga). Optionally narrow to a single matchday. Returns teams, kickoff datetime, final score, and whether each match is finished. It is categorised as a Read tool in the Mcp Openligadb MCP Server, which means it retrieves data without modifying state.
get_matches accepts 3 parameters: league, season, matchday. Required: league, season. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Openligadb MCP server in PolicyLayer and add a rule for get_matches: 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 Mcp Openligadb. Nothing to install.
get_matches 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_matches 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_matches. 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_matches is provided by the Mcp Openligadb MCP server (https://gateway.pipeworx.io/openligadb/mcp). 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 →