Low Risk

web_search

web_search

How to control web_search ↓

What web_search does on Cricket

AI agents call web_search 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.

Low Risk

Why web_search needs a policy

Web search tools retrieve data without modifying, deleting, or executing operations. The name clearly indicates a search operation aligned with the server's purpose of fetching cricket data. Confidence is moderate (0.85) because the description is empty; however, naming and context strongly suggest a Read classification. No financial, destructive, or code-execution implications evident.

From the tool's definition Tool name 'web_search' performs information retrieval; no description provided but naming convention and server context (cricket data fetching) indicate query/search functionality typical of Read operations.

Documented attack patterns abuse exactly the kind of access web_search gives an agent:

How to control web_search

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 web_search:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "web_search": {}
  }
}

web_search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Cricket — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about web_search

What does the web_search tool do? +

web_search. It is categorised as a Read tool in the Cricket MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on web_search? +

Register the Cricket MCP server in PolicyLayer and add a rule for web_search: 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.

What risk level is web_search? +

web_search is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit web_search? +

Yes. Add a rate_limit block to the web_search 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.

How do I block web_search completely? +

Set action: deny in the PolicyLayer policy for web_search. 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.

What MCP server provides web_search? +

web_search 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.

Enforce policy on every Cricket tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.