highlightly_get_head_to_head

Get head-to-head history between two teams for a sport.

SERVERSports Hub SOURCEmcp-sports-hub
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade B, identity unverified Pull the record →

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.

Questions about highlightly_get_head_to_head

What does the highlightly_get_head_to_head tool do? +

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.

How do I enforce a policy on highlightly_get_head_to_head? +

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.

What risk level is highlightly_get_head_to_head? +

highlightly_get_head_to_head is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit highlightly_get_head_to_head? +

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.

How do I block highlightly_get_head_to_head completely? +

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.

What MCP server provides highlightly_get_head_to_head? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Sports Hub's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.