AI agents call getPage 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 data from a Logseq knowledge base with no side effects or ability to modify content. It matches the Read category definition: 'retrieves or queries data; no side effects.' The confidence is slightly reduced (0.9 instead of 1.0) due to the empty description, but the tool name and context strongly indicate a read operation.
From the tool's definition Tool name 'getPage' combined with server context describing 'retrieval' of content from a knowledge graph. No description provided, but sibling tools include clear read operations (getAllPages, getBacklinks, analyzeGraph) and no destructive verbs.
Documented attack patterns abuse exactly the kind of access getPage gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Logseq MCP Tools, and nothing reaches the server without passing your rules. This is the rule we recommend for getPage:
{
"version": "1",
"default": "deny",
"tools": {
"getPage": {}
}
}getPage is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
getPage. 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 getPage: 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.
getPage 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 getPage 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 getPage. 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.
getPage is provided by the Logseq MCP Tools MCP server (joelhooks/logseq-mcp-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Logseq MCP Tools, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 Logseq MCP Tools tools catalogued and risk-classified — across an index of 43,000+ MCP servers.