get_live_commentary
AI agents call get_live_commentary 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 retrieves cricket match commentary data without modifying, executing commands, or causing irreversible changes. It fits the Read category. Severity is low because even if misused, fetching sports commentary data carries no security, financial, or operational risk. Confidence is 0.85 (not higher) due to empty description, but the naming convention and server context provide strong supporting evidence.
From the tool's definition Tool named 'get_live_commentary' on a cricket data server alongside other data-retrieval tools (get_cricket_news, get_cricket_schedule, get_icc_rankings, get_live_matches, get_match_details, get_player_stats). The 'get_' prefix indicates read-only retrieval.
Documented attack patterns abuse exactly the kind of access get_live_commentary 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_commentary:
{
"version": "1",
"default": "deny",
"tools": {
"get_live_commentary": {}
}
}get_live_commentary 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_commentary. 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_commentary: 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_commentary 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_commentary 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_commentary. 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_commentary 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.