// SCAN REPORT

GROWI MCP Server

26 tools. 11 can modify or destroy data without limits.

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

Last updated: 2 Jul 2026

11 can modify or destroy data

15 read-only

26 tools total

Community server · catalogue entry verified 02/07/2026

How to control GROWI MCP Server ↓

TOOL MAP

What GROWI MCP Server exposes to your agents

Read (15) Write / Execute (8) Destructive / Financial (3)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous GROWI MCP Server tools

Destructive · High deletePages Deletion of wiki pages is an irreversible, destructive operation that cannot be undone without restoration from backups. Destructive · High deleteShareLinkById Deletion of share links is an irreversible operation that cannot be undone. Destructive · High deleteShareLinks This tool permanently removes share links, which cannot be undone. Write · Medium unpublishPage Unpublishing a page removes it from public visibility but does not delete the page or its data — the content remains in the system and can be republished.

11 of GROWI MCP Server's 26 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control GROWI MCP Server

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

Deny destructive operations

{
  "deletePages": {
    "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

{
  "createPage": {
    "limits": [
      {
        "counter": "createpage_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "getComments": {
    "limits": [
      {
        "counter": "getcomments_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

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

Create a free account and register GROWI MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON GROWI →

Instant setup, no code required.

FULL CATALOGUE

All 26 GROWI MCP Server tools

DESTRUCTIVE 3 tools

Destructive deletePages Delete pages in GROWI Destructive deleteShareLinkById Delete a specific share link by ID in GROWI Destructive deleteShareLinks Delete all share links for a page in GROWI

WRITE 8 tools

Write createPage Create a new page in GROWI Write createShareLink Create a share link for a page in GROWI Write duplicatePage Duplicate a page. Can recursively duplicate the page with its descendants. Write publishPage Publish a page by its ID Write renamePage Rename or move a page in GROWI Write unpublishPage Unpublish a page by its ID Write updatePage Update an existing page in GROWI Write updateTag Update tags for a page in GROWI

READ 15 tools

Read getComments Get comments for a page revision in GROWI Read getPage Get page data about the specific GROWI page Read getPageInfo Get summary information about a specific GROWI page Read getPageListingChildren Get children pages for a specified page by ID or path in GROWI Read getPageListingRoot Get root page listing information from GROWI Read getPageTag Get tags for a specific page in GROWI Read getRecentPages Get recently updated pages from GROWI with pagination support Read getRevision Get detailed information about a specific revision in GROWI Read getShareLinks Get share links for a specific page in GROWI Read getTagList Get list of tags in GROWI with pagination support Read getUserRecentPages Get recently created pages by a specific user in GROWI Read listRevisions List revisions for a page in GROWI with pagination support Read pageListingInfo Get summary information for pages in GROWI by IDs or path Read searchPages Search pages in GROWI using Elasticsearch Read searchTags Search for tags in GROWI

EXPLORE

Related servers

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

FAQ

Questions about GROWI MCP Server

Can an AI agent delete data through the GROWI MCP Server MCP server? +

Yes. The GROWI MCP Server server exposes 3 destructive tools including deletePages, deleteShareLinkById, deleteShareLinks. 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 GROWI MCP Server? +

The GROWI MCP Server server has 8 write tools including createPage, createShareLink, duplicatePage. 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 GROWI MCP Server.

How many tools does the GROWI MCP Server MCP server expose? +

26 tools across 3 categories: Destructive, Read, Write. 15 are read-only. 11 can modify, create, or delete data.

How do I enforce a policy on GROWI MCP Server? +

Register the GROWI MCP Server 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 GROWI MCP Server tool call.

Deterministic rules across all 26 GROWI MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON GROWI →

Instant setup, no code required.

26 GROWI MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.