web_search

A read tool on the Container- MCP server.

SERVERContainer-MCP SOURCE54rt1n/container-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/54rt1n-container-mcp/web-search.md

WHAT IT DOES

What web_search does on Container-MCP

AI agents call web_search to retrieve information from Container-MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why web_search is rated Low

Web search operations are fundamentally retrieval-based with no side effects—they query external data sources and return results. The empty description lowers confidence slightly, but the semantics of 'web_search' align clearly with the Read category. Severity is low because misuse primarily risks information disclosure or resource exhaustion, not data corruption or financial harm.

From the tool's definition Tool name 'web_search' typically retrieves information from web sources without modifying data. No description provided, but the name strongly suggests a read-only query operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs web_search safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Container-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For web_search, this is the rule to start with:

web_search Allowed

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "web_search": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Container-MCP, apply this rule, and every web_search call is checked against it from then on.

FAQ

Questions about web_search

What does the web_search tool do? +

web_search is a read tool on the Container MCP server. It is categorised as a Read tool in the Container-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on web_search? +

Register the Container 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 Container-MCP. 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 Container MCP server (54rt1n/container-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Container, and thousands of servers like it.

This server

All 27 Container tools →

Across the catalogue

web_search on Azure AI Agent Service + Azure AI Search MCP Server →evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →