get_match_stats

Game tab: stats. Get live or final match stats such as possession, shots, corners, fouls, offsides, yellow cards, saves, pass accuracy, and elapsed minute. Use for live or finished games; scheduled games may have no stats yet.

Server Tulidu Sport tulidu-sport/tulidu-sport-mcp
Category Read
Risk class Low
Parameters 00 required

What get_match_stats does on Tulidu Sport

AI agents call get_match_stats to retrieve information from Tulidu Sport without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_match_stats needs a policy

This tool retrieves sports statistics from completed or ongoing matches. It performs read-only queries against the Tulidu Sport platform with no side effects, no data modification, and no external operations triggered. The information returned is non-sensitive aggregate sports data. Misuse by an AI agent would at worst result in unnecessary API calls, presenting minimal risk.

From the tool's definition Tool description states it 'Get[s] live or final match stats' including possession, shots, corners, fouls, offsides, yellow cards, saves, pass accuracy, and elapsed minute.

Questions about get_match_stats

What does the get_match_stats tool do? +

Game tab: stats. Get live or final match stats such as possession, shots, corners, fouls, offsides, yellow cards, saves, pass accuracy, and elapsed minute. Use for live or finished games; scheduled games may have no stats yet. It is categorised as a Read tool in the Tulidu Sport MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_match_stats? +

Register the Tulidu Sport MCP server in PolicyLayer and add a rule for get_match_stats: 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 Tulidu Sport. Nothing to install.

What risk level is get_match_stats? +

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

Can I rate-limit get_match_stats? +

Yes. Add a rate_limit block to the get_match_stats 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 get_match_stats completely? +

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

get_match_stats is provided by the Tulidu Sport MCP server (tulidu-sport/tulidu-sport-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

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.