esports_get_match
Get details for a specific esports match by ID.
This record as markdown: /tools/creativelead-unclick/esports-get-match.md
What esports_get_match does on UnClick
AI agents call esports_get_match 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 |
|---|---|---|---|
api_key | string | — | |
match_id | number | — |
Parameters from the server's own tool schema.
Why esports_get_match is rated Low
This tool queries and retrieves information about an esports match. The verb 'Get' and the passive retrieval nature of the operation confirm this is a Read category tool. There is no data modification, code execution, deletion, or financial transaction. Severity is low because retrieving public esports match information poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'esports_get_match' and description 'Get details for a specific esports match by ID' indicate a retrieval operation with no side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs esports_get_match 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_get_match, this is the rule to start with:
esports_get_match 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_get_match call is checked against it from then on.
Questions about esports_get_match
Get details for a specific esports match by ID. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
esports_get_match accepts 2 parameters: api_key, match_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 esports_get_match: 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_get_match 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_get_match 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_get_match. 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_get_match is provided by the UnClick MCP server (creativelead/unclick). 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