Requarks Wiki

29 tools. 10 can modify or destroy data without limits.

3 destructive tools with no built-in limits. Policy required.

Last updated:

10 can modify or destroy data
19 read-only
29 tools total

Community server · catalogue entry verified 30/06/2026

How to control Requarks Wiki ↓

What Requarks Wiki exposes to your agents

Read (19) Write / Execute (7) Destructive / Financial (3)
Critical Risk

The most dangerous Requarks Wiki tools

10 of Requarks Wiki's 29 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Requarks Wiki

PolicyLayer is an MCP gateway — it sits between your AI agents and Requarks Wiki, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations
{
  "wikijs_delete_comment": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "wikijs_create_comment": {
    "limits": [
      {
        "counter": "wikijs_create_comment_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "wikijs_get_comment": {
    "limits": [
      {
        "counter": "wikijs_get_comment_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Requarks Wiki — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON REQUARKS WIKI →

Instant setup, no code required.

All 29 Requarks Wiki tools

READ 19 tools
Read wikijs_get_comment Get a single comment by ID. Returns full comment details including content and author information. Read wikijs_get_current_user Get the profile of the currently authenticated API user. Returns identity, permissions context, and activity i Read wikijs_get_navigation Retrieve the navigation tree for all locales. Returns configured navigation items including links, headers, an Read wikijs_get_page_by_id Get a single page body/content by numeric page ID. Read wikijs_get_page_by_path Get a single page body/content using path + locale. Read wikijs_get_page_history Get edit history trail for a page by ID. Returns version dates, authors, and change types. Read wikijs_get_page_links Get all pages and their outbound links for a locale. Returns an array of pages with their link relationships. Read wikijs_get_page_tree Get the page tree hierarchy for site navigation and structure discovery. Returns folders and/or pages with dep Read wikijs_get_page_version Get a specific version of a page by page ID and version ID. Returns full page content and metadata for that ve Read wikijs_get_site_config Retrieve safe (non-sensitive) site configuration including title, description, feature flags, and upload limit Read wikijs_get_system_info Retrieve Wiki.js system information including version, database type, and usage statistics. Useful for diagnos Read wikijs_list_asset_folders List asset folders within a parent folder. Returns folder structure for navigating the asset hierarchy. Read wikijs_list_assets List assets (files, images) in a specific folder. Returns asset metadata including filename, type, size, and u Read wikijs_list_comments List all comments for a specific page by path and locale. Returns comment details including author info and ti Read wikijs_list_pages List pages for crawling/indexing with optional locale and limit. Read wikijs_list_tags List all tags used across wiki pages. Useful for discovering content categories and taxonomy. Read wikijs_search_pages Search pages by keyword and return path/title summary for knowledge lookup. Read wikijs_search_tags Search for tags matching a query string. Returns an array of matching tag name strings. Read wikijs_search_users Search for users by name or email. Returns matching user profiles for collaboration context.

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about Requarks Wiki

Can an AI agent delete data through the Requarks Wiki MCP server? +

Yes. The Requarks Wiki server exposes 3 destructive tools including wikijs_delete_comment, wikijs_delete_page, wikijs_delete_tag. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Requarks Wiki? +

The Requarks Wiki server has 7 write tools including wikijs_create_comment, wikijs_create_page, wikijs_move_page. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Requarks Wiki.

How many tools does the Requarks Wiki MCP server expose? +

29 tools across 3 categories: Destructive, Read, Write. 19 are read-only. 10 can modify, create, or delete data.

How do I enforce a policy on Requarks Wiki? +

Register the Requarks Wiki MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Requarks Wiki tool call.

Deterministic rules across all 29 Requarks Wiki tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

29 Requarks Wiki tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.