New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

wikimedia-analytics.pageviews.aggregate

Get total pageview counts for a Wikimedia project (e.g. en.wikipedia, de.wikipedia, commons.wikimedia) over a date range, bucketed daily or monthly. Filter by access method (desktop, mobile-web, mobile-app, or all-access) and traffic agent (user, spider, automated, or all-agents). Data: Wikimedia...

SERVERApibase SOURCEapibase-mcp-client
Low RISK CLASS
Category Read
Parameters 63 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.aggregate.md

What wikimedia-analytics.pageviews.aggregate does on Apibase

AI agents call wikimedia-analytics.pageviews.aggregate 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.

ParameterTypeRequiredDescription
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)
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.

Why wikimedia-analytics.pageviews.aggregate is rated Low

Retrieves aggregated public pageview statistics from Wikimedia without side effects or authentication.

From the tool's definition Get total pageview counts, date range, no auth required, REST API query

Questions about wikimedia-analytics.pageviews.aggregate

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

Get total pageview counts for a Wikimedia project (e.g. en.wikipedia, de.wikipedia, commons.wikimedia) over a date range, bucketed daily or monthly. Filter by access method (desktop, mobile-web, mobile-app, or all-access) and traffic agent (user, spider, automated, or all-agents). 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.aggregate accept? +

wikimedia-analytics.pageviews.aggregate accepts 6 parameters: end, agent, start, access, project, granularity. Required: end, start, 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.aggregate? +

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

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

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

Yes. Add a rate_limit block to the wikimedia-analytics.pageviews.aggregate 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.aggregate completely? +

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

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

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Apibase's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.