highlightly_get_head_to_head
Get head-to-head history between two teams for a sport.
This record as markdown: /tools/io-github-lacausecrypto-sports-hub/highlightly-get-head-to-head.md
What highlightly_get_head_to_head does on Sports Hub
AI agents call highlightly_get_head_to_head 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_head_to_head is rated Low
This tool retrieves historical sports data (head-to-head matchup records) between two teams. It performs a read-only query operation with no side effects, data modification, code execution, or irreversible actions. The 'get_' prefix and verb 'Get' confirm it is a retrieval operation. No sensitive operations are involved, making the severity low.
From the tool's definition Tool name includes 'get_' prefix and description states 'Get head-to-head history between two teams' indicating data retrieval with no modification or execution.
Attacks that exploit this kind of access
The rule that runs highlightly_get_head_to_head 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_head_to_head, this is the rule to start with:
highlightly_get_head_to_head 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_head_to_head call is checked against it from then on.
Questions about highlightly_get_head_to_head
Get head-to-head history between two teams for a sport. 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_head_to_head: 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_head_to_head 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_head_to_head 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_head_to_head. 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_head_to_head 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