sgo_get_event

Get details for a specific event by ID.

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/sgo-get-event.md

WHAT IT DOES

What sgo_get_event does on Sports Hub

AI agents call sgo_get_event 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 sgo_get_event is rated Low

This tool retrieves event details by ID without creating, modifying, deleting, or executing any operations. It is a standard read-only query typical of sports data APIs. The low severity reflects minimal blast radius if misused—an agent could only retrieve information already exposed by the API.

From the tool's definition Tool name 'sgo_get_event' and description 'Get details for a specific event by ID' indicate a retrieval operation. The verb 'Get' and the retrieval context (fetching event details by identifier) align with data retrieval with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

sgo_get_event Allowed

sgo_get_event 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": {
    "sgo_get_event": {}
  }
}

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 sgo_get_event call is checked against it from then on.

FAQ

Questions about sgo_get_event

What does the sgo_get_event tool do? +

Get details for a specific event by ID. 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 sgo_get_event? +

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

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

Can I rate-limit sgo_get_event? +

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

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

sgo_get_event 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_event_details on CTFtime MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

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