find_related_pages
AI agents call find_related_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 tool name suggests discovering or retrieving related pages through search or graph traversal—a read-only operation with no side effects. While the description is uninformative, the sibling tools and server purpose (knowledge graph exploration, content retrieval) strongly indicate this is a data retrieval function rather than creation, modification, or deletion.
From the tool's definition Tool name 'find_related_pages' indicates a search/retrieval operation consistent with sibling Read tools like 'get_page_by_path', 'get_wiki_page', and 'get_recent_changes'.
Attacks that exploit this kind of access
find_related_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 find_related_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.
find_related_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 find_related_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 find_related_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.
find_related_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 →