Get the current matchday's football / soccer matches (results / scores) for a league (e.g. this week's Bundesliga fixtures) in the current season.
AI agents call current_matchday 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). |
Parameters from the server's own tool schema.
This tool queries public match data from OpenLigaDB and returns information about fixtures and scores. It performs data retrieval only, with no ability to create, modify, delete, or execute operations. The read-only nature and absence of destructive or side-effect capabilities make this a straightforward Read category risk with low severity.
From the tool's definition Tool retrieves 'current matchday's football / soccer matches (results / scores)' - a read-only query operation with no side effects or modification capability.
Attacks that exploit this kind of access
Get the current matchday's football / soccer matches (results / scores) for a league (e.g. this week's Bundesliga fixtures) in the current season. It is categorised as a Read tool in the Mcp Openligadb MCP Server, which means it retrieves data without modifying state.
current_matchday accepts 1 parameter: league. Required: league. 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 current_matchday: 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.
current_matchday 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 current_matchday 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 current_matchday. 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.
current_matchday 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 →