get_page_blocks
AI agents call get_page_blocks 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 retrieves blocks from a page in Logseq without modifying data. The naming pattern and sibling tool analysis indicate it performs a read-only query operation on the knowledge graph. No side effects are expected from retrieving page blocks. Low severity due to lack of destructive or system-level impact.
From the tool's definition Tool name 'get_page_blocks' combined with context of sibling read tools (get_all_pages, get_page, get_block) and empty description indicating a retrieval operation. The 'get_' prefix is consistent with query/fetch semantics.
Attacks that exploit this kind of access
get_page_blocks. 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_blocks: 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_blocks 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_blocks 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_blocks. 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_blocks 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 →