get_page
AI agents call get_page 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.
get_page retrieves or queries data about a page from the local Logseq instance. No side effects occur—the operation does not create, modify, delete, or execute anything. This is a standard data retrieval operation. Confidence is 0.85 rather than higher only because the description is empty, but the tool name and sibling context strongly indicate a read-only GET operation.
From the tool's definition Tool name 'get_page' combined with sibling context showing similar read-only operations (get_all_pages, get_block, get_page_blocks, get_page_linked_references). The tool retrieves page data from a Logseq knowledge graph without modification.
Attacks that exploit this kind of access
get_page. 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_page: 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_page 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 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. 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 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 →