livegolf_get_tournament

Get details for a specific golf tournament.

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/livegolf-get-tournament.md

WHAT IT DOES

What livegolf_get_tournament does on Sports Hub

AI agents call livegolf_get_tournament 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.

RISK

Why livegolf_get_tournament is rated Low

This tool retrieves and queries tournament information without creating, modifying, deleting, or executing operations. It is a straightforward data fetch operation consistent with other Read-category tools on the same server (e.g., apifootball_get_fixtures, apifootball_get_leagues). The blast radius of misuse is minimal—an AI agent cannot cause harm by querying tournament details.

From the tool's definition Tool name 'livegolf_get_tournament' and description 'Get details for a specific golf tournament' indicate a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs livegolf_get_tournament 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 livegolf_get_tournament, this is the rule to start with:

livegolf_get_tournament Allowed

livegolf_get_tournament is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "livegolf_get_tournament": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sports Hub, apply this rule, and every livegolf_get_tournament call is checked against it from then on.

FAQ

Questions about livegolf_get_tournament

What does the livegolf_get_tournament tool do? +

Get details for a specific golf tournament. 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 livegolf_get_tournament? +

Register the Sports Hub MCP server in PolicyLayer and add a rule for livegolf_get_tournament: 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 livegolf_get_tournament? +

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

Can I rate-limit livegolf_get_tournament? +

Yes. Add a rate_limit block to the livegolf_get_tournament 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 livegolf_get_tournament completely? +

Set action: deny in the PolicyLayer policy for livegolf_get_tournament. 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 livegolf_get_tournament? +

livegolf_get_tournament 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.

KEEP EXPLORING

More on Sports Hub, and thousands of servers like it.

This server

All 396 Sports Hub tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →