List pages for crawling/indexing with optional locale and limit.
AI agents call wikijs_list_pages to retrieve information from Requarks Wiki without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query operation to retrieve a list of pages, consistent with standard Read category behavior. The parameters (locale, limit) control filtering and pagination of results, not data modification. No side effects, destructive actions, or external operations are triggered. Severity is low because listing pages is a benign retrieval operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'wikijs_list_pages' and description 'List pages for crawling/indexing with optional locale and limit' indicate a retrieval operation that returns page metadata for indexing purposes without modifying any data.
Attacks that exploit this kind of access
List pages for crawling/indexing with optional locale and limit. It is categorised as a Read tool in the Requarks Wiki MCP Server, which means it retrieves data without modifying state.
Register the Requarks Wiki MCP server in PolicyLayer and add a rule for wikijs_list_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 Requarks Wiki. Nothing to install.
wikijs_list_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 wikijs_list_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 wikijs_list_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.
wikijs_list_pages is provided by the Requarks Wiki MCP server (uyu423/requarks-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 →