list_wiki_pages
AI agents call list_wiki_pages to retrieve information from WikiJS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list_wiki_pages' tool function is to retrieve or enumerate existing wiki pages without modifying them. This is a non-destructive, non-side-effect read operation. Even though the description is empty (lowering confidence slightly), the semantic meaning of the tool name and its position among sibling tools strongly indicates it performs data retrieval only.
From the tool's definition Tool name 'list_wiki_pages' indicates retrieval/enumeration of wiki pages. Description is empty, but sibling tools include write operations (create_wiki_page, delete_wiki_page) and read operations (get_page_by_path, get_page_history, get_recent_changes),…
Attacks that exploit this kind of access
list_wiki_pages. It is categorised as a Read tool in the WikiJS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WikiJS MCP Server MCP server in PolicyLayer and add a rule for list_wiki_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 WikiJS MCP Server. Nothing to install.
list_wiki_pages is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_wiki_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.
Set action: deny in the PolicyLayer policy for list_wiki_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.
list_wiki_pages 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 →