AI agents call get_team_form 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 queries a DuckDB database to fetch and analyze cricket team performance statistics. It has no side effects—it does not create, modify, delete, or execute arbitrary operations. The read-only nature (retrieving last N match results and computed statistics) and informational purpose (understanding team form) place it firmly in the Read category with low severity risk.
From the tool's definition Tool retrieves historical match results, performance metrics ('win/loss streak, average scores, run rate trends'), and form data with no modification capabilities.
Attacks that exploit this kind of access
How has this team been performing recently? Last N match results with win/loss streak, average scores, and run rate trends. 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_team_form: 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_team_form 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_team_form 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_team_form. 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_team_form 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 →