This record as markdown: /tools/2234839-mcpserver/web-search.md
What web_search does on Martin MCP Toolbox
AI agents call web_search to retrieve information from Martin MCP Toolbox without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why web_search is rated Low
This tool performs web search and returns results—a read-only operation with no modification, deletion, or external command execution. The description explicitly states it returns 'raw search results' without automatic composition, confirming it is a passive information retrieval function. Blast radius is minimal as misuse would only expose retrieved public information.
From the tool's definition Tool name 'web_search' and description stating '快速检索并返回原始搜索结果' (rapidly retrieve and return raw search results) indicates data retrieval without side effects or content generation.
Attacks that exploit this kind of access
The rule that runs web_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Martin MCP Toolbox, 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 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Martin MCP Toolbox, apply this rule, and every web_search call is checked against it from then on.
Questions about web_search
快速检索并返回原始搜索结果(不做自动成文)。. It is categorised as a Read tool in the Martin MCP Toolbox MCP Server, which means it retrieves data without modifying state.
Register the Martin MCP Toolbox 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 Martin MCP Toolbox. Nothing to install.
web_search 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 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.
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.
web_search is provided by the Martin MCP Toolbox MCP server (2234839/mcpserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Martin MCP Toolbox, and thousands of servers like it.
This server
Across the catalogue