sportsdb_team_events
Get upcoming events for a team by TheSportsDB team ID.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/sportsdb-team-events.md
What sportsdb_team_events does on UnClick
AI agents call sportsdb_team_events to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | TheSportsDB team ID |
Parameters from the server's own tool schema.
Why sportsdb_team_events is rated Low
This tool queries a sports database to retrieve upcoming event information for a specified team. It performs a simple data retrieval operation with no capacity to modify, delete, or execute arbitrary code. The blast radius of misuse is minimal—an agent could at worst retrieve irrelevant or unwanted sports data, but cannot alter state, execute commands, or cause financial impact.
From the tool's definition Tool name 'sportsdb_team_events' and description 'Get upcoming events for a team by TheSportsDB team ID' indicate a query operation that retrieves public sports scheduling data.
Attacks that exploit this kind of access
The rule that runs sportsdb_team_events safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sportsdb_team_events, this is the rule to start with:
sportsdb_team_events 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 UnClick, apply this rule, and every sportsdb_team_events call is checked against it from then on.
Questions about sportsdb_team_events
Get upcoming events for a team by TheSportsDB team ID. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
sportsdb_team_events accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for sportsdb_team_events: 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 UnClick. Nothing to install.
sportsdb_team_events 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_team_events 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_team_events. 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_team_events is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue