This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/esports-matches.md
What esports_matches does on UnClick
AI agents call esports_matches 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 |
|---|---|---|---|
game | string | — | e.g. lol, csgo, dota2 |
page | number | — | |
status | string | — | running, upcoming, past |
api_key | string | — | |
per_page | number | — |
Parameters from the server's own tool schema.
Why esports_matches is rated Low
This tool retrieves esports match data from an external API (PandaScore) without creating, modifying, deleting, or executing arbitrary operations. It is a straightforward read operation with no side effects, making it the lowest-risk category. Low severity reflects the benign nature of accessing public sports data.
From the tool's definition Tool name 'esports_matches' and description 'Get esports matches from PandaScore' indicate data retrieval with no modification. The verb 'Get' confirms query/fetch semantics.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs esports_matches 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 esports_matches, this is the rule to start with:
esports_matches 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 esports_matches call is checked against it from then on.
Questions about esports_matches
Get esports matches from PandaScore. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
esports_matches accepts 5 parameters: game, page, status, api_key, per_page. 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 esports_matches: 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.
esports_matches 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 esports_matches 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 esports_matches. 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.
esports_matches 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