// MCP TOOL REFERENCE

OPENWEBSEARCH TOOLS

6 tools from the OpenWebSearch MCP Server, categorised by risk level.

View the OpenWebSearch policy → Token cost: 398 tokens →
// ALL 6 OPENWEBSEARCH TOOLS
READ 6 tools
Read fetchCsdnArticle Fetch full article content from a csdn post URL Read fetchGithubReadme Fetch README content from a GitHub repository URL Read fetchJuejinArticle Fetch full article content from a Juejin(掘金) post URL Read fetchLinuxDoArticle Fetch full article content from a linux.do post URL Read fetchWebContent Fetch content from a public HTTP(S) URL (supports Markdown files and normal web pages) Read search Search the web using multiple engines (e.g., Baidu, Bing, DuckDuckGo, CSDN, Exa, Brave, Juejin(掘金)) with no...

Route OpenWebSearch through PolicyLayer and every one of its 6 tools is checked against your policy before it runs.

CHECK YOUR STACK →

See every tool, the dangerous ones, and the token cost across your stack.

// FAQ
How many tools does the OpenWebSearch MCP server have? +

The OpenWebSearch MCP server exposes 6 tools across 1 categories: Read.

How do I enforce policies on OpenWebSearch tools? +

Route the OpenWebSearch server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do OpenWebSearch tools fall into? +

OpenWebSearch tools are categorised as Read (6). Each category has a recommended default policy.

Enforce policy on every OpenWebSearch tool call.

Start from OpenWebSearch, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.