web_search_multilang
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 H...
This record as markdown: /tools/io-github-getgapup-gapup-mcp/web-search-multilang.md
What web_search_multilang does on Gapup Mcp
AI agents call web_search_multilang to retrieve information from Gapup Mcp 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.
Why web_search_multilang is rated Low
This is a query and retrieval tool. It gathers publicly available information from search engines and knowledge bases without modifying data or executing code. While it supports multiple languages and sources, the core function remains passive information retrieval. The mention of 'agent-payable' and financial/compliance tools elsewhere on the server does not affect this individual tool's classification.
From the tool's definition Tool performs multi-language web search aggregation across multiple sources (Mojeek, Wikipedia, DDG, HN) and returns ranked results. Key verbs: 'search', 'aggregates results', 'returns deduplicated results'.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
The rule that runs web_search_multilang safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gapup Mcp, 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 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 Gapup Mcp, apply this rule, and every web_search_multilang call is checked against it from then on.
Questions about web_search_multilang
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 Gapup Mcp MCP Server, which means it retrieves data without modifying state.
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.
Register the Gapup 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 Gapup Mcp. Nothing to install.
web_search_multilang 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_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.
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.
web_search_multilang is provided by the Gapup MCP server (https://mcp.gapup.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gapup, and thousands of servers like it.
This server
Across the catalogue