AI agents call get_milestone_tracker 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 is a read-only query tool that retrieves and analyzes existing cricket statistics. It performs no write, destructive, execute, or financial operations. The function merely queries milestone data against a local database to surface player achievement information. Blast radius of misuse is negligible—an AI agent cannot cause harm by repeatedly querying milestone data.
From the tool's definition Tool name 'get_milestone_tracker' and description 'Find players approaching or who have reached landmarks like 10000 runs, 500 wickets, 100 centuries' indicate querying/retrieval of historical career statistics from the DuckDB database with no data…
Attacks that exploit this kind of access
Who is close to a career milestone? Find players approaching or who have reached landmarks like 10000 runs, 500 wickets, 100 centuries, etc. 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_milestone_tracker: 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_milestone_tracker 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_milestone_tracker 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_milestone_tracker. 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_milestone_tracker is provided by the Cricket MCP server (mavaali/cricket-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 →