get_page_by_path
AI agents call get_page_by_path 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 strongly suggests a GET/retrieval operation that fetches a wiki page by its path without modification. No parameters are described, but the pattern of similar 'get_*' tools on the server and the absence of side-effect keywords (create, update, delete) indicate this is a read-only query.
From the tool's definition Tool name 'get_page_by_path' indicates a retrieval operation. Sibling tools include read-only operations like 'get_wiki_page', 'get_page_history', 'get_recent_changes', 'export_page_content', and 'explore_knowledge_graph', suggesting this tool follows the…
Attacks that exploit this kind of access
get_page_by_path. 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_by_path: 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_by_path 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_by_path 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_by_path. 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_by_path is provided by the WikiJS MCP Server MCP server (vnikhilbuddhavarapu/wiki-gcp-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 →