web_search_multilang

SERVERMcp Knowledge SOURCEhttps://mcp.gapup.io

Low RISK CLASS

Category Read

Parameters 51 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-getgapup-mcp-knowledge/web-search-multilang.md

WHAT IT DOES

What web_search_multilang does on Mcp Knowledge

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

Parameter	Type	Required	Description
`lang`	string	—	2-letter language code. If omitted, auto-detected from query characters and lexical markers.
`async`	boolean	—	If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti
`query`	string	Yes	Search query in any language
`country`	string	—	ISO-3166-1 alpha-2 country code for geographic bias (e.g. FR, DE, JP, BR). Optional.
`max_results`	integer	—	Maximum number of results to return (default 10).

Parameters from the server's own tool schema.

RISK

Why web_search_multilang is rated Low

This tool performs information retrieval only—it queries multiple search engines and aggregates results without side effects. It is a classic Read operation: it retrieves and returns data without creating, modifying, deleting, or executing anything. The blast radius of misuse is minimal (e.g., gathering information on competitors or public data). No financial, destructive, or execution risk is present.

From the tool's definition Tool description states it 'searches' and 'aggregates results' from web sources; returns 'deduplicated results ranked by cross-engine consensus.' The verb 'search' and the passive retrieval of publicly-available data indicate no data modification, deletion,…

Risk signalsAccepts freeform code/query input (query)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs web_search_multilang safely

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

web_search_multilang Allowed

web_search_multilang 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_multilang": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Knowledge, apply this rule, and every web_search_multilang call is checked against it from then on.

FAQ

Questions about web_search_multilang

What does the web_search_multilang tool do? +

Multi-language, multi-source web search that goes beyond Anglo-centric results. Supports 15 languages (fr/de/es/it/pt/nl/ja/zh/ko/ar/ru/sv/pl/tr/en) with automatic detection. Aggregates results from Mojeek (independent search engine, multilang) and Wikipedia (native multilang API), with DDG and HN as English-language complements. Returns deduplicated results ranked by cross-engine consensus. Use when you need non-English search results, when DDG fails, or for geographically-biased queries. Phase 2 #7 of the geo/lang expansion plan. Note: Brave/Bing/Searx are blocked from DO IPs — configure AICI_RESEARCH_PROXY_URL for residential proxy. It is categorised as a Read tool in the Mcp Knowledge MCP Server, which means it retrieves data without modifying state.

What parameters does web_search_multilang accept? +

web_search_multilang accepts 5 parameters: lang, async, query, country, max_results. Required: query. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on web_search_multilang? +

Register the Mcp Knowledge MCP server in PolicyLayer and add a rule for web_search_multilang: 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 Mcp Knowledge. Nothing to install.

What risk level is web_search_multilang? +

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

Can I rate-limit web_search_multilang? +

Yes. Add a rate_limit block to the web_search_multilang 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_multilang completely? +

Set action: deny in the PolicyLayer policy for web_search_multilang. 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_multilang? +

web_search_multilang is provided by the Mcp Knowledge MCP server (https://mcp.gapup.io). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Knowledge, and thousands of servers like it.

This server

All 271 Mcp Knowledge tools →

Across the catalogue

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

Guides

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