Returns recent change events, newest first, in segments of 50. Defaults to edits and page creations; set types to include log actions, categorizations, or external changes. Each row includes title, timestamp, user, revision IDs, size change, flags (minor/bot/new/anon), tags, and change type. Filt...
AI agents call get-recent-changes 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 retrieves and queries historical change data from MediaWiki with various filter options (timestamp, namespace, user, tags) and pagination. It has no side effects—it only reads and returns existing change records. The description explicitly states it 'Returns' data with no mention of creating, modifying, or deleting content. This is a classic Read operation.
From the tool's definition Returns recent change events with filtering and pagination; purely informational retrieval of edit history, timestamps, user information, and change metadata. No modification, execution, or deletion of data.
Documented attack patterns abuse exactly the kind of access get-recent-changes 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 get-recent-changes:
{
"version": "1",
"default": "deny",
"tools": {
"get-recent-changes": {}
}
}get-recent-changes 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 recent change events, newest first, in segments of 50. Defaults to edits and page creations; set types to include log actions, categorizations, or external changes. Each row includes title, timestamp, user, revision IDs, size change, flags (minor/bot/new/anon), tags, and change type. Filter by timestamp window, namespaces, user, change tag, or hide flags (hideBots/hideMinor/hideAnon/hideRedirects/hidePatrolled). Pass showPatrolStatus to include per-row patrol state (requires patrol rights). Paginate with the continue token from the truncation marker. For a single page. 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 get-recent-changes: 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.
get-recent-changes 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 get-recent-changes 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 get-recent-changes. 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.
get-recent-changes 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.