wikimedia-analytics.pageviews.top
List the most-viewed articles on a Wikimedia project for a single day, or for a full month with day="all-days". Returns each article title, view count, and rank. Filter by access method (desktop, mobile-web, mobile-app, or all-access). Data: Wikimedia Analytics REST API (wikimedia.org/api/rest_v1...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/wikimedia-analytics.pageviews.top.md
What wikimedia-analytics.pageviews.top does on Apibase
AI agents call wikimedia-analytics.pageviews.top 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 |
|---|---|---|---|
day | string | Yes | 2-digit day (e.g. 01), or "all-days" for the monthly top list |
year | string | Yes | 4-digit year (e.g. 2026) |
month | string | Yes | 2-digit month (e.g. 08) |
access | string | — | Access method filter (default all-access) |
project | string | Yes | Wikimedia project domain (e.g. en.wikipedia, de.wikipedia, commons.wikimedia) |
Parameters from the server's own tool schema.
Why wikimedia-analytics.pageviews.top is rated Low
Retrieves public pageview statistics from Wikimedia with no side effects or data modification capability.
From the tool's definition List the most-viewed articles...view count...no auth required
Attacks that exploit this kind of access
The rule that runs wikimedia-analytics.pageviews.top 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-analytics.pageviews.top, this is the rule to start with:
wikimedia-analytics.pageviews.top 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-analytics.pageviews.top call is checked against it from then on.
Questions about wikimedia-analytics.pageviews.top
List the most-viewed articles on a Wikimedia project for a single day, or for a full month with day="all-days". Returns each article title, view count, and rank. Filter by access method (desktop, mobile-web, mobile-app, or all-access). Data: Wikimedia Analytics REST API (wikimedia.org/api/rest_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-analytics.pageviews.top accepts 5 parameters: day, year, month, access, project. Required: day, year, month, project. 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-analytics.pageviews.top: 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-analytics.pageviews.top 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-analytics.pageviews.top 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-analytics.pageviews.top. 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-analytics.pageviews.top 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