wikimedia-analytics.edits.aggregate

SERVERApibase SOURCEapibase-mcp-client

Medium RISK CLASS

Category Write

Parameters 63 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/wikimedia-analytics.edits.aggregate.md

WHAT IT DOES

What wikimedia-analytics.edits.aggregate does on Apibase

AI agents use wikimedia-analytics.edits.aggregate to create or update resources in Apibase, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apibase environment.

Parameter	Type	Required	Description
`end`	string	Yes	End date in YYYYMMDD format (e.g. 20260801)
`start`	string	Yes	Start date in YYYYMMDD format (e.g. 20260801)
`project`	string	Yes	Wikimedia project domain (e.g. en.wikipedia, de.wikipedia, commons.wikimedia)
`page_type`	string	—	Page namespace type filter (default all-page-types)
`editor_type`	string	—	Editor type filter (default all-editor-types)
`granularity`	string	—	Time bucket granularity (default monthly)

Parameters from the server's own tool schema.

RISK

Why wikimedia-analytics.edits.aggregate is rated Medium

An AI agent can call wikimedia-analytics.edits.aggregate faster than any human can review: one bad instruction and it creates or modifies resources in Apibase by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

wikimedia-analytics.edits.aggregate Rate-limited

wikimedia-analytics.edits.aggregate stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wikimedia-analytics.edits.aggregate": {
      "limits": [
        {
          "counter": "wikimedia-analytics.edits.aggregate_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT 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.edits.aggregate call is checked against it from then on.

FAQ

Questions about wikimedia-analytics.edits.aggregate

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

Get total edit counts for a Wikimedia project over a date range, bucketed daily or monthly. Filter by editor type (anonymous, group-bot, name-bot, user, or all-editor-types) and page type (content, non-content, or all-page-types). Data: Wikimedia Analytics REST API (wikimedia.org/api/rest_v1), no auth required. It is categorised as a Write tool in the Apibase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does wikimedia-analytics.edits.aggregate accept? +

wikimedia-analytics.edits.aggregate accepts 6 parameters: end, start, project, page_type, editor_type, 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.edits.aggregate? +

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

wikimedia-analytics.edits.aggregate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

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

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

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

wikimedia-analytics.edits.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.

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

Govern customer-ops agents →Argument validation →Scoped token →