remove_block
AI agents call remove_block to permanently remove resources in Logseq MCP Tools — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool removes a block from a Logseq knowledge graph, which is an irreversible operation that destroys data. Although the description is empty, the name and context of sibling tools (particularly 'delete_page') strongly indicate this performs permanent deletion.
From the tool's definition Tool name 'remove_block' indicates deletion/removal of data; sibling tools include 'delete_page' confirming this server handles destructive operations; the verb 'remove' is consistently used for irreversible deletions in the Logseq context.
Attacks that exploit this kind of access
remove_block. It is categorised as a Destructive tool in the Logseq MCP Tools MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Logseq MCP Tools MCP server in PolicyLayer and add a rule for remove_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.
remove_block is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_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 remove_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.
remove_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 →