create_page_summary · WikiJS MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_page_summary does on WikiJS MCP Server

AI agents use create_page_summary to create or update resources in WikiJS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WikiJS MCP Server environment.

WHY IT NEEDS A POLICY

Why create_page_summary needs a policy

The tool appears to create or generate summary content based on the name and server's stated capability to support 'creating...wiki pages' and 'page summaries.' This is a Write operation as it generates new data (a summary), likely stored or displayed within the wiki system. Severity is medium because summaries typically don't destroy data or have severe blast radius, though incorrect summaries could mislead users.

From the tool's definition Tool name 'create_page_summary' and server context indicating 'creating...wiki pages' and 'content exporting for documentation workflows' suggest content creation. Description is empty, lowering confidence.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_page_summary Rate-limited

create_page_summary stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_page_summary": {
      "limits": [
        {
          "counter": "create_page_summary_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches WikiJS MCP Server, so you can run agents against it safely.

FAQ

Questions about create_page_summary

What does the create_page_summary tool do? +

create_page_summary. It is categorised as a Write tool in the WikiJS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_page_summary? +

Register the WikiJS MCP Server MCP server in PolicyLayer and add a rule for create_page_summary: 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 WikiJS MCP Server. Nothing to install.

What risk level is create_page_summary? +

create_page_summary is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_page_summary? +

Yes. Add a rate_limit block to the create_page_summary 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 create_page_summary completely? +

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

create_page_summary is provided by the WikiJS MCP Server MCP server (vnikhilbuddhavarapu/wiki-gcp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.