create_block
AI agents use create_block 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.
create_block creates new data in a Logseq knowledge graph. This is reversible (blocks can be deleted via remove_block), so it falls under Write rather than Destructive. The severity is medium because misuse could clutter or corrupt a knowledge base structure, but damage can be undone. Confidence is reduced slightly (0.85 vs higher) due to the empty tool description, though the name and server context are clear.
From the tool's definition Tool name 'create_block' combined with server context describing 'creating pages, managing blocks' indicates data creation.
Attacks that exploit this kind of access
create_block. 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_block: 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_block 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_block 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_block. 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_block 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 →