AI agents call get_career_impact 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 performs statistical analysis and aggregation of cricket performance data stored in DuckDB. It retrieves information about a player's career impact across matches but does not create, modify, delete, or execute external operations. The action is purely analytical and read-only, returning computed insights from existing match data. No side effects or irreversible actions are possible.
From the tool's definition Tool aggregates and analyzes existing cricket statistics (impact scores, batting/bowling/fielding contributions) to provide career summary information.
Attacks that exploit this kind of access
How impactful is this player across their career? Aggregates per-match impact scores to show average impact, peak match, and batting/bowling/fielding contribution breakdown. 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_career_impact: 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_career_impact 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_career_impact 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_career_impact. 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_career_impact 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 →