Get live cricket matches from Cricbuzz.
AI agents call get_live_matches to retrieve information from Cricket without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool fetches and queries cricket match data from Cricbuzz without any side effects, creation, modification, or deletion of data. It is a simple data retrieval operation that retrieves current live match information. There is no risk of financial impact, destructive actions, code execution, or data modification. The severity is low as misuse would only result in reading publicly available cricket data.
From the tool's definition Tool name 'get_live_matches' and description 'Get live cricket matches from Cricbuzz' indicate data retrieval with no modification, deletion, or execution of external operations.
Documented attack patterns abuse exactly the kind of access get_live_matches gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cricket, and nothing reaches the server without passing your rules. This is the rule we recommend for get_live_matches:
{
"version": "1",
"default": "deny",
"tools": {
"get_live_matches": {}
}
}get_live_matches is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get live cricket matches from Cricbuzz. It is categorised as a Read tool in the Cricket MCP Server, which means it retrieves data without modifying state.
Register the Cricket MCP server in PolicyLayer and add a rule for get_live_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 Cricket. Nothing to install.
get_live_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 get_live_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 get_live_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.
get_live_matches is provided by the Cricket MCP server (tarun7r/cricket-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Cricket, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
9 Cricket tools catalogued and risk-classified — across an index of 43,000+ MCP servers.