get-pages

ServerMediawiki Mcp Server Olioex
CategoryRead

WHAT IT DOES

What get-pages does on Mediawiki Mcp Server Olioex

AI agents call get-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.

THE RISK

Low Risk

Why get-pages needs a policy

The tool performs read-only operations on wiki pages: it retrieves and returns existing page data in wikitext format or metadata form. There are no side effects, no data modification, creation, deletion, or execution of external operations. This is a straightforward data retrieval operation with minimal security risk if misused by an AI agent, as it only exposes already-public wiki content.

From the tool's definition Tool description states 'Returns multiple wiki pages' and is 'Suited to reading a cluster of related pages, diffing a page family, or syncing pages to local storage.' This explicitly describes retrieval of wikitext source or metadata without modification or…

Documented attack patterns abuse exactly the kind of access get-pages gives an agent:

POLICY

How to control get-pages

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-pages:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-pages": {}
  }
}

get-pages is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Mediawiki Mcp Server Olioex — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Mediawiki Mcp Server Olioex tools

Destructive delete-page Removes a wiki page from public view and returns the deleted title. This is a soft delete: Destructive neowiki-delete-subject Deletes one NeoWiki Subject by ID from its page. Enabled only when the wiki has NeoWiki in Destructive undelete-page Restores a previously deleted wiki page, including its full revision history, and returns Execute cargo-query Returns rows from one or more Cargo tables on the targeted wiki, matching a SQL-style filt Execute smw-query Runs a Semantic MediaWiki Write create-page Creates a new wiki page with the provided content and returns the new page Write move-page Renames a wiki page, moving it — and by default its talk page — to a new title, and return Write neowiki-set-main-subject Sets which existing Subject on a wiki page is its Main Subject, or clears it. Enabled only

All 38 Mediawiki Mcp Server Olioex tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get-pages

What does the get-pages tool do? +

Returns multiple wiki pages in one call (wikitext source or metadata only). Suited to reading a cluster of related pages, diffing a page family, or syncing pages to local storage. Accepts up to ${MAX_TITLES} titles; missing pages are reported inline (not as errors). Each page. It is categorised as a Read tool in the Mediawiki Mcp Server Olioex MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-pages? +

Register the Mediawiki Mcp Server Olioex MCP server in PolicyLayer and add a rule for get-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.

What risk level is get-pages? +

get-pages is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get-pages? +

Yes. Add a rate_limit block to the get-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.

How do I block get-pages completely? +

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

What MCP server provides get-pages? +

get-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.

Enforce policy on every Mediawiki Mcp Server Olioex tool call.

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.

CHECK YOUR STACK →

Free to start. No card required.

38 Mediawiki Mcp Server Olioex tools catalogued and risk-classified — across an index of 43,000+ MCP servers.