wikimedia-rest.pages.search
Full-text search across Wikipedia article titles and content. Returns matching page titles, highlighted excerpts, short descriptions, and thumbnails, ranked by relevance. Select the language edition with lang (default en). Data: MediaWiki REST API (wikipedia.org/w/rest.php/v1), no auth required.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/wikimedia-rest.pages.search.md
What wikimedia-rest.pages.search does on Apibase
AI agents call wikimedia-rest.pages.search 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 |
|---|---|---|---|
lang | string | — | Wikipedia language edition subdomain code (default en, e.g. de, fr, ja, zh-yue) |
limit | integer | — | Maximum number of results to return, 1-50 (default 10) |
query | string | Yes | Full-text search query (e.g. "einstein relativity") |
Parameters from the server's own tool schema.
Why wikimedia-rest.pages.search is rated Low
Query-only operation retrieving public Wikipedia data without side effects or modifications.
From the tool's definition Full-text search across Wikipedia article titles and content. Returns matching page titles, highlighted excerpts.
Attacks that exploit this kind of access
The rule that runs wikimedia-rest.pages.search 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 wikimedia-rest.pages.search, this is the rule to start with:
wikimedia-rest.pages.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 Apibase, apply this rule, and every wikimedia-rest.pages.search call is checked against it from then on.
Questions about wikimedia-rest.pages.search
Full-text search across Wikipedia article titles and content. Returns matching page titles, highlighted excerpts, short descriptions, and thumbnails, ranked by relevance. Select the language edition with lang (default en). Data: MediaWiki REST API (wikipedia.org/w/rest.php/v1), no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
wikimedia-rest.pages.search accepts 3 parameters: lang, limit, query. 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 wikimedia-rest.pages.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 Apibase. Nothing to install.
wikimedia-rest.pages.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 wikimedia-rest.pages.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 wikimedia-rest.pages.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.
wikimedia-rest.pages.search 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