wikipedia.article.summary
Fetch the introductory summary of any Wikipedia article — returns plain-text extract, short description, thumbnail image URL, Wikidata item ID, and the canonical article URL. Supports 55+ Wikipedia language editions via the optional language parameter. Ideal for quick entity lookups: people, plac...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/wikipedia.article.summary.md
What wikipedia.article.summary does on Apibase
AI agents call wikipedia.article.summary 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 |
|---|---|---|---|
title | string | Yes | Wikipedia article title exactly as it appears in the URL (e.g. "Python_(programming_language)", "Albert_Einstein"). Use underscores for spaces. Case-sensitive. |
language | string | — | Two-letter Wikipedia language code (e.g. "en" for English, "de" for German, "fr" for French). Defaults to English ("en"). |
Parameters from the server's own tool schema.
Why wikipedia.article.summary is rated Low
Retrieves public Wikipedia data without side effects or modifications.
From the tool's definition Fetch introductory summary, returns plain-text extract, no auth required.
Attacks that exploit this kind of access
The rule that runs wikipedia.article.summary 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.article.summary, this is the rule to start with:
wikipedia.article.summary 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.article.summary call is checked against it from then on.
Questions about wikipedia.article.summary
Fetch the introductory summary of any Wikipedia article — returns plain-text extract, short description, thumbnail image URL, Wikidata item ID, and the canonical article URL. Supports 55+ Wikipedia language editions via the optional language parameter. Ideal for quick entity lookups: people, places, concepts, events, organizations. No auth required. Data: Wikipedia contributors, CC BY-SA 4.0 (attribution included in response). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
wikipedia.article.summary accepts 2 parameters: title, language. Required: title. 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.article.summary: 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.article.summary 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.article.summary 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.article.summary. 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.article.summary 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