sportsrc_get_match
Get detailed match information including streams, venue, and lineups.
This record as markdown: /tools/io-github-lacausecrypto-sports-hub/sportsrc-get-match.md
What sportsrc_get_match does on Sports Hub
AI agents call sportsrc_get_match 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 sportsrc_get_match is rated Low
This tool retrieves and queries static match data (streams, venue, lineups) without side effects. It is analogous to sibling tools like apifootball_get_fixtures and apifootball_get_fixture_lineups, which are clearly Read operations. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal — returning incorrect sports data does not compromise systems or cause financial harm.
From the tool's definition Tool name and description use 'Get' which indicates retrieval. Description explicitly states 'Get detailed match information including streams, venue, and lineups' — purely a query operation with no modification, deletion, or execution of external actions.
Attacks that exploit this kind of access
The rule that runs sportsrc_get_match 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 sportsrc_get_match, this is the rule to start with:
sportsrc_get_match 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 sportsrc_get_match call is checked against it from then on.
Questions about sportsrc_get_match
Get detailed match information including streams, venue, and lineups. 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 sportsrc_get_match: 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.
sportsrc_get_match 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 sportsrc_get_match 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 sportsrc_get_match. 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.
sportsrc_get_match 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