get_page_history
AI agents call get_page_history 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 'get_' prefix strongly suggests a retrieval operation. Even without a description, this tool appears to fetch historical data rather than create, modify, or delete content. Page history retrieval is a non-destructive, read-only query operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'get_page_history' indicates retrieval of historical data about a wiki page. The sibling tools include create, delete, and update operations, but this tool follows the Read pattern (get_*).
Attacks that exploit this kind of access
get_page_history. 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 get_page_history: 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.
get_page_history 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_page_history 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_page_history. 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_page_history 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 →