get_related_pages
AI agents call get_related_pages to retrieve information from Grokipedia MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns related pages from Grokipedia, a read-only information retrieval operation. No side effects, data modification, code execution, or destructive actions are indicated. The empty description lowers confidence slightly, but the context of sibling retrieval tools and the server's stated purpose of information retrieval strongly supports the Read category.
From the tool's definition Tool name 'get_related_pages' combined with sibling tools (get_page, get_page_citations, get_page_content, get_page_section) and server description emphasizing 'searching and retrieving articles' and 'information retrieval' indicate this retrieves related…
Attacks that exploit this kind of access
get_related_pages. It is categorised as a Read tool in the Grokipedia MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Grokipedia MCP Server MCP server in PolicyLayer and add a rule for get_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 Grokipedia MCP Server. Nothing to install.
get_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 get_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 get_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.
get_related_pages is provided by the Grokipedia MCP Server MCP server (theonetrueniz/mcp-grokipedia-tool). 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 →