opendota_get_match

Get full detail for a Dota 2 match: players, heroes, K/D/A, items, gold/xp, objectives.

SERVERSports Hub SOURCEmcp-sports-hub
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/io-github-lacausecrypto-sports-hub/opendota-get-match.md

What opendota_get_match does on Sports Hub

AI agents call opendota_get_match 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 opendota_get_match is rated Low

This tool queries and retrieves historical Dota 2 match data including player statistics, hero selections, and game metrics. There is no indication of state modification, data deletion, code execution, or financial impact. It is purely a read operation that fetches sports analytics information, consistent with other sibling tools (get_odds, get_fixtures, get_players) on the Sports Hub server.

From the tool's definition Tool name 'opendota_get_match' and description 'Get full detail for a Dota 2 match: players, heroes, K/D/A, items, gold/xp, objectives' — uses 'Get' verb and retrieves match statistics and player performance data with no modification or side effects.

Questions about opendota_get_match

What does the opendota_get_match tool do? +

Get full detail for a Dota 2 match: players, heroes, K/D/A, items, gold/xp, objectives. It is categorised as a Read tool in the Sports Hub MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on opendota_get_match? +

Register the Sports Hub MCP server in PolicyLayer and add a rule for opendota_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 Sports Hub. Nothing to install.

What risk level is opendota_get_match? +

opendota_get_match is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit opendota_get_match? +

Yes. Add a rate_limit block to the opendota_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.

How do I block opendota_get_match completely? +

Set action: deny in the PolicyLayer policy for opendota_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.

What MCP server provides opendota_get_match? +

opendota_get_match 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Sports Hub's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.