AI agents call get_partnerships 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.
The tool performs a read-only query to retrieve aggregated partnership statistics. It has no side effects, does not modify data, does not execute code or commands, and does not delete or move anything. The blast radius of misuse is minimal—an AI agent could request irrelevant queries but cannot cause harm through this tool alone. This is a straightforward data retrieval operation consistent with the Read category.
From the tool's definition Tool queries and retrieves historical cricket statistics ('biggest batting partnerships', 'total runs', 'venue', 'match context') from a local DuckDB database without modifying, deleting, or executing arbitrary operations.
Attacks that exploit this kind of access
What are the biggest batting partnerships? Highest partnerships by total runs, showing both batters, runs, balls, venue, and match context. 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_partnerships: 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_partnerships 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_partnerships 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_partnerships. 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_partnerships 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 →