Get upcoming cricket match schedule from Cricbuzz.
AI agents call get_cricket_schedule 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 schedules from Cricbuzz—a read-only operation with no side effects. It does not create, modify, or delete data, nor does it execute code or trigger external operations. The maximum impact of misuse would be information disclosure or resource exhaustion, both low-severity concerns.
From the tool's definition Tool name 'get_cricket_schedule' and description 'Get upcoming cricket match schedule from Cricbuzz' indicate retrieval of publicly available scheduling data with no modification, deletion, or execution of code.
Documented attack patterns abuse exactly the kind of access get_cricket_schedule 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_cricket_schedule:
{
"version": "1",
"default": "deny",
"tools": {
"get_cricket_schedule": {}
}
}get_cricket_schedule 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 upcoming cricket match schedule 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_cricket_schedule: 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_cricket_schedule 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_cricket_schedule 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_cricket_schedule. 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_cricket_schedule 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.