Search pages by keyword and return path/title summary for knowledge lookup.
AI agents call wikijs_search_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 full-text search operation returning page metadata (path/title summaries). It is a retrieval-only function with no capability to modify, delete, or execute code. The verb 'search' and the output description ('return path/title summary') confirm it is a Read operation. Severity is low as misuse would only expose existing, likely intended-to-be-public wiki content.
From the tool's definition Tool name 'wikijs_search_pages' and description 'Search pages by keyword and return path/title summary for knowledge lookup' indicate a query operation that retrieves data without modification or side effects.
Attacks that exploit this kind of access
Search pages by keyword and return path/title summary for knowledge lookup. 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_search_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_search_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_search_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_search_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_search_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 →