opendota.players.matches
Recent match history for a Dota 2 player — array of matches with match_id, hero, kills/deaths/assists, duration, win/loss, party_size, game_mode, lobby_type. Sortable by date.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/opendota.players.matches.md
What opendota.players.matches does on Apibase
AI agents call opendota.players.matches to retrieve information from Apibase 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 |
|---|---|---|---|
limit | integer | — | Max matches to return (1-100, default 20). |
account_id | integer | Yes | Steam account ID (Dota 2 32-bit). Get from /api/search?q=playername. Example: 105248644 (Dendi). |
Parameters from the server's own tool schema.
Why opendota.players.matches is rated Low
Retrieves historical Dota 2 player match data; no side effects or modifications.
From the tool's definition Recent match history, array of matches with match_id, hero, kills/deaths/assists
Attacks that exploit this kind of access
The rule that runs opendota.players.matches safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For opendota.players.matches, this is the rule to start with:
opendota.players.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 Apibase, apply this rule, and every opendota.players.matches call is checked against it from then on.
Questions about opendota.players.matches
Recent match history for a Dota 2 player — array of matches with match_id, hero, kills/deaths/assists, duration, win/loss, party_size, game_mode, lobby_type. Sortable by date. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
opendota.players.matches accepts 2 parameters: limit, account_id. Required: account_id. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for opendota.players.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 Apibase. Nothing to install.
opendota.players.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 opendota.players.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 opendota.players.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.
opendota.players.matches is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue