Game tab: events. Get match timeline events such as goals, cards, substitutions, penalties, players, assists, and elapsed minute. Best for live or finished games; scheduled games may return an empty list.
AI agents call get_match_events 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.
This tool queries and retrieves historical or live sports event data with no side effects. It falls squarely into the Read category as it only fetches information from the Tulidu Sport platform. The severity is low because misuse would only expose sports data without operational, financial, or system impact.
From the tool's definition Tool retrieves match timeline events including goals, cards, substitutions, penalties, players, assists, and elapsed minute for games. Described as 'Get' operation with no mutation, creation, deletion, or execution capabilities mentioned.
Attacks that exploit this kind of access
Game tab: events. Get match timeline events such as goals, cards, substitutions, penalties, players, assists, and elapsed minute. Best for live or finished games; scheduled games may return an empty list. It is categorised as a Read tool in the Tulidu Sport MCP Server, which means it retrieves data without modifying state.
Register the Tulidu Sport MCP server in PolicyLayer and add a rule for get_match_events: 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.
get_match_events 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 get_match_events 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 get_match_events. 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.
get_match_events 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.
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 →