wikimedia-analytics.pageviews.per_article

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 74 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/wikimedia-analytics.pageviews.per-article.md

WHAT IT DOES

What wikimedia-analytics.pageviews.per_article does on Apibase

AI agents call wikimedia-analytics.pageviews.per_article 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
`end`	string	Yes	End date in YYYYMMDD format (e.g. 20260801)
`agent`	string	—	Traffic agent filter (default all-agents)
`start`	string	Yes	Start date in YYYYMMDD format (e.g. 20260801)
`access`	string	—	Access method filter (default all-access)
`article`	string	Yes	Article title, spaces or underscores accepted (e.g. Albert_Einstein)
`project`	string	Yes	Wikimedia project domain (e.g. en.wikipedia, de.wikipedia, commons.wikimedia)
`granularity`	string	—	Time bucket granularity (default daily)

Parameters from the server's own tool schema.

RISK

Why wikimedia-analytics.pageviews.per_article is rated Low

Retrieves historical pageview statistics; read-only data with no side effects or sensitive operations.

From the tool's definition Get pageview history for one specific article, no auth required.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs wikimedia-analytics.pageviews.per_article 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.per_article, this is the rule to start with:

wikimedia-analytics.pageviews.per_article Allowed

wikimedia-analytics.pageviews.per_article is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wikimedia-analytics.pageviews.per_article": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every wikimedia-analytics.pageviews.per_article call is checked against it from then on.

FAQ

Questions about wikimedia-analytics.pageviews.per_article

What does the wikimedia-analytics.pageviews.per_article tool do? +

Get pageview history for one specific article on a Wikimedia project over a date range, bucketed daily or monthly. Filter by access method and traffic agent. Use after wikimedia-analytics.pageviews_top to track trend history for a discovered article. 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.

What parameters does wikimedia-analytics.pageviews.per_article accept? +

wikimedia-analytics.pageviews.per_article accepts 7 parameters: end, agent, start, access, article, project, granularity. Required: end, start, article, project. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on wikimedia-analytics.pageviews.per_article? +

Register the Apibase MCP server in PolicyLayer and add a rule for wikimedia-analytics.pageviews.per_article: 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.

What risk level is wikimedia-analytics.pageviews.per_article? +

wikimedia-analytics.pageviews.per_article is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit wikimedia-analytics.pageviews.per_article? +

Yes. Add a rate_limit block to the wikimedia-analytics.pageviews.per_article 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.

How do I block wikimedia-analytics.pageviews.per_article completely? +

Set action: deny in the PolicyLayer policy for wikimedia-analytics.pageviews.per_article. 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.

What MCP server provides wikimedia-analytics.pageviews.per_article? +

wikimedia-analytics.pageviews.per_article 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.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →