wikipedia.search.pages
Search Wikipedia for articles matching a keyword or phrase — returns ranked results with article titles, Wikidata descriptions, content excerpts, and thumbnail images. Supports 55+ language editions. Up to 50 results per query. No auth required. Data: Wikipedia contributors, CC BY-SA 4.0.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/wikipedia.search.pages.md
What wikipedia.search.pages does on Apibase
AI agents call wikipedia.search.pages to retrieve information from Apibase 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 |
|---|---|---|---|
limit | integer | — | Maximum number of results to return (1–50, default 10). |
query | string | Yes | Search query string (e.g. "machine learning", "World War II", "quantum physics"). Searches article titles and content snippets. |
language | string | — | Two-letter Wikipedia language code (default "en" for English). Use "es" for Spanish, "zh" for Chinese, "ar" for Arabic, etc. |
Parameters from the server's own tool schema.
Why wikipedia.search.pages is rated Low
Tool only retrieves and returns public Wikipedia search results without modifying data.
From the tool's definition Search Wikipedia for articles matching a keyword or phrase — returns ranked results
Attacks that exploit this kind of access
The rule that runs wikipedia.search.pages safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wikipedia.search.pages, this is the rule to start with:
wikipedia.search.pages 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 Apibase, apply this rule, and every wikipedia.search.pages call is checked against it from then on.
Questions about wikipedia.search.pages
Search Wikipedia for articles matching a keyword or phrase — returns ranked results with article titles, Wikidata descriptions, content excerpts, and thumbnail images. Supports 55+ language editions. Up to 50 results per query. No auth required. Data: Wikipedia contributors, CC BY-SA 4.0. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
wikipedia.search.pages accepts 3 parameters: limit, query, language. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for wikipedia.search.pages: 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 Apibase. Nothing to install.
wikipedia.search.pages 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 wikipedia.search.pages 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 wikipedia.search.pages. 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.
wikipedia.search.pages is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue