update_wiki_page
AI agents use update_wiki_page 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.
This tool creates or modifies wiki page data reversibly. Although the description is empty, the name combined with the server's stated purpose of supporting 'updating' and the presence of related write/delete operations (create_wiki_page, delete_wiki_page) confirms it as a Write operation.
From the tool's definition Tool name 'update_wiki_page' indicates modification of wiki content. Server description states it 'support[s] operations like page creation, searching, and updating.' Sibling tools include destructive operations (delete_wiki_page), but update operations are…
Attacks that exploit this kind of access
update_wiki_page. 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.
Register the WikiJS MCP Server MCP server in PolicyLayer and add a rule for update_wiki_page: 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.
update_wiki_page is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_wiki_page 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 update_wiki_page. 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.
update_wiki_page is provided by the WikiJS MCP Server MCP server (vnikhilbuddhavarapu/wiki-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →