Returns the changes between two versions of a wiki page as a compact text diff. Each side accepts a revision ID, page title (latest revision), or supplied wikitext; text-vs-text is rejected. Only the changes are returned over the wire. For the full text of both sides, fetch with get-page instead....
AI agents call compare-pages to retrieve information from Mediawiki Mcp Server Olioex without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and compares data between two page versions. It performs no writes, executions, or deletions. The description explicitly notes 'for the full text of both sides, fetch with get-page instead', confirming it is a read-only comparison operation.
From the tool's definition Returns the changes between two versions of a wiki page as a compact text diff
Documented attack patterns abuse exactly the kind of access compare-pages gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mediawiki Mcp Server Olioex, and nothing reaches the server without passing your rules. This is the rule we recommend for compare-pages:
{
"version": "1",
"default": "deny",
"tools": {
"compare-pages": {}
}
}compare-pages is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Returns the changes between two versions of a wiki page as a compact text diff. Each side accepts a revision ID, page title (latest revision), or supplied wikitext; text-vs-text is rejected. Only the changes are returned over the wire. For the full text of both sides, fetch with get-page instead. If a title or revision ID does not exist, an error is returned. Set includeDiff=false for a cheap change-detection response that skips diff rendering and returns just the change flag, revision metadata, and size delta. Diff output is truncated at 50000 bytes by default with a trailing marker; a narrower revision range or includeDiff=false avoids truncation. It is categorised as a Read tool in the Mediawiki Mcp Server Olioex MCP Server, which means it retrieves data without modifying state.
Register the Mediawiki Mcp Server Olioex MCP server in PolicyLayer and add a rule for compare-pages: 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 Mediawiki Mcp Server Olioex. Nothing to install.
compare-pages 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 compare-pages 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 compare-pages. 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.
compare-pages is provided by the Mediawiki Mcp Server Olioex MCP server (mediawiki-mcp-server-olioex). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mediawiki Mcp Server Olioex, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
38 Mediawiki Mcp Server Olioex tools catalogued and risk-classified — across an index of 43,000+ MCP servers.