create_page
AI agents use create_page to create or update resources in Logseq MCP Tools — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Logseq MCP Tools environment.
This tool creates new pages in a Logseq knowledge graph, which is a reversible write operation. It does not delete data (ruling out Destructive), execute code (ruling out Execute), move money (ruling out Financial), or merely read data (ruling out Read). The severity is medium because creating unwanted pages could clutter a knowledge base but the damage is easily reversible by deleting the page.
From the tool's definition Tool name is 'create_page' and it is listed among Logseq operations that include creating pages and managing blocks. The server description explicitly states it enables 'creating pages' as a core operation.
Attacks that exploit this kind of access
create_page. It is categorised as a Write tool in the Logseq MCP Tools MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Logseq MCP Tools MCP server in PolicyLayer and add a rule for create_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.
create_page is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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 →