openliga_get_match_data
Get detailed data for a specific match by its ID, including goals, results, and location.
This record as markdown: /tools/io-github-lacausecrypto-sports-hub/openliga-get-match-data.md
What openliga_get_match_data does on Sports Hub
AI agents call openliga_get_match_data to retrieve information from Sports Hub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why openliga_get_match_data is rated Low
This tool queries and returns match information (scores, goals, location) without creating, modifying, deleting, or executing any operations. It has no side effects and poses minimal security risk even if called repeatedly or with unexpected arguments.
From the tool's definition Tool retrieves 'detailed data for a specific match by its ID, including goals, results, and location' — purely read operations with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs openliga_get_match_data safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sports Hub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For openliga_get_match_data, this is the rule to start with:
openliga_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 Sports Hub, apply this rule, and every openliga_get_match_data call is checked against it from then on.
Questions about openliga_get_match_data
Get detailed data for a specific match by its ID, including goals, results, and location. It is categorised as a Read tool in the Sports Hub MCP Server, which means it retrieves data without modifying state.
Register the Sports Hub MCP server in PolicyLayer and add a rule for openliga_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 Sports Hub. Nothing to install.
openliga_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 openliga_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 openliga_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.
openliga_get_match_data is provided by the Sports Hub MCP server (mcp-sports-hub). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sports Hub, and thousands of servers like it.
This server
Across the catalogue