Gets all pages from the Logseq graph.
AI agents call get_all_pages to retrieve information from Logseq MCP Tools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing data from the knowledge graph without modifying, deleting, or executing anything. It is a pure read operation with minimal blast radius—the worst case is information disclosure about the structure of a user's local Logseq instance.
From the tool's definition Tool name 'get_all_pages' and description 'Gets all pages from the Logseq graph' indicate a retrieval operation with no side effects. The verb 'Gets' denotes a query/fetch action.
Attacks that exploit this kind of access
Gets all pages from the Logseq graph. It is categorised as a Read tool in the Logseq MCP Tools MCP Server, which means it retrieves data without modifying state.
Register the Logseq MCP Tools MCP server in PolicyLayer and add a rule for get_all_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 Logseq MCP Tools. Nothing to install.
get_all_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_all_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_all_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_all_pages is provided by the Logseq MCP Tools MCP server (mikeysrecipes/logseq-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 →