highlightly_get_matches
Get matches/fixtures for a sport, filtered by date, league or season.
This record as markdown: /tools/io-github-lacausecrypto-sports-hub/highlightly-get-matches.md
What highlightly_get_matches does on Sports Hub
AI agents call highlightly_get_matches 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 highlightly_get_matches is rated Low
This tool purely retrieves and queries sports match/fixture data with optional filters. It has no capability to modify, delete, execute code, or affect financial systems. The filtering parameters (date, league, season) are search/query parameters, not operations that change data or trigger external actions. This is a straightforward Read operation with minimal risk.
From the tool's definition Tool name contains 'get' and description states 'Get matches/fixtures' with filtering by date, league, or season. No side effects, no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
The rule that runs highlightly_get_matches 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 highlightly_get_matches, this is the rule to start with:
highlightly_get_matches 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 highlightly_get_matches call is checked against it from then on.
Questions about highlightly_get_matches
Get matches/fixtures for a sport, filtered by date, league or season. 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 highlightly_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 Sports Hub. Nothing to install.
highlightly_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 highlightly_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 highlightly_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.
highlightly_get_matches 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