Medium Risk

page_revisions

Recent edit history of a Wikipedia article. Use for "when was this article last edited", "who edited the X page", or to check whether an article has been recently disputed/vandalized before quoting it.

Part of the Wikimedia Rest server.

page_revisions can modify Wikimedia Rest data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE WIKIMEDIA REST →

Free to start. No card required.

AI agents use page_revisions to create or modify resources in Wikimedia Rest. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call page_revisions repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Wikimedia Rest.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "page_revisions": {
      "limits": [
        {
          "counter": "page_revisions_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Wikimedia Rest policy for all 31 tools.

Get this rule live on your own Wikimedia Rest server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY WIKIMEDIA REST →

View all 31 tools →

These attack patterns abuse exactly the kind of access page_revisions gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so page_revisions only ever does what you allow.

SECURE WIKIMEDIA REST →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the page_revisions tool do? +

Recent edit history of a Wikipedia article. Use for "when was this article last edited", "who edited the X page", or to check whether an article has been recently disputed/vandalized before quoting it.. It is categorised as a Write tool in the Wikimedia Rest MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on page_revisions? +

Register the Wikimedia Rest MCP server in PolicyLayer and add a rule for page_revisions: 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 Wikimedia Rest. Nothing to install.

What risk level is page_revisions? +

page_revisions is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit page_revisions? +

Yes. Add a rate_limit block to the page_revisions 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 page_revisions completely? +

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

page_revisions is provided by the Wikimedia Rest MCP server (https://gateway.pipeworx.io/wikimedia-rest/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Wikimedia Rest tool call.

Deterministic rules across all 31 Wikimedia Rest tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.