sportsdb_get_event_details
Get full details for a specific event by its TheSportsDB ID. Includes scores, venue, thumbnails, and video highlights.
This record as markdown: /tools/io-github-lacausecrypto-sports-hub/sportsdb-get-event-details.md
What sportsdb_get_event_details does on Sports Hub
AI agents call sportsdb_get_event_details 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 sportsdb_get_event_details is rated Low
This tool retrieves and queries event data by ID from TheSportsDB. It has no side effects, does not modify data, execute code, delete resources, or move money. It is a straightforward Read operation with minimal risk if misused by an AI agent — returning publicly available sports data.
From the tool's definition Tool description states 'Get full details for a specific event' — a retrieval operation that 'Includes scores, venue, thumbnails, and video highlights.' No write, deletion, execution, or financial operations are described or implied.
Attacks that exploit this kind of access
The rule that runs sportsdb_get_event_details 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 sportsdb_get_event_details, this is the rule to start with:
sportsdb_get_event_details 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 sportsdb_get_event_details call is checked against it from then on.
Questions about sportsdb_get_event_details
Get full details for a specific event by its TheSportsDB ID. Includes scores, venue, thumbnails, and video highlights. 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 sportsdb_get_event_details: 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.
sportsdb_get_event_details 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 sportsdb_get_event_details 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 sportsdb_get_event_details. 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.
sportsdb_get_event_details 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