Get the league table / standings for a football / soccer league and season (e.g. the Bundesliga table). Returns each team's position, played, won, draw, lost, goals, goal difference, and points.
AI agents call get_table 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". |
Parameters from the server's own tool schema.
This tool retrieves pre-existing sports league standings data from a public, keyless sports database. It performs no writes, deletes, executions, or financial operations. The data returned is informational only and read-only in nature. Confidence is high because the description clearly indicates data retrieval with no modifications possible.
From the tool's definition Tool name 'get_table' and description 'Get the league table / standings for a football / soccer league and season...
Attacks that exploit this kind of access
Get the league table / standings for a football / soccer league and season (e.g. the Bundesliga table). Returns each team's position, played, won, draw, lost, goals, goal difference, and points. It is categorised as a Read tool in the Mcp Openligadb MCP Server, which means it retrieves data without modifying state.
get_table accepts 2 parameters: league, season. 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_table: 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_table 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_table 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_table. 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_table 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 →