move_block · Logseq MCP Tools MCP: Risk & Policy

WHAT IT DOES

What move_block does on Logseq MCP Tools

AI agents use move_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.

WHY IT NEEDS A POLICY

Why move_block needs a policy

Moving a block modifies the document structure but is reversible—the block content and relationships remain intact. This is a write operation (reversible data modification) rather than destructive (irreversible deletion). Confidence is moderate (0.72) because the tool description is empty, requiring inference from name and server context.

From the tool's definition Tool name 'move_block' with context from sibling tools (create_block, insert_block, remove_block, delete_page) indicates data manipulation. The operation moves/reorders a block within a knowledge graph structure, modifying the document state reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_block Rate-limited

move_block stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "move_block": {
      "limits": [
        {
          "counter": "move_block_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Logseq MCP Tools, so you can run agents against it safely.

FAQ

Questions about move_block

What does the move_block tool do? +

move_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.

How do I enforce a policy on move_block? +

Register the Logseq MCP Tools MCP server in PolicyLayer and add a rule for move_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.

What risk level is move_block? +

move_block is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit move_block? +

Yes. Add a rate_limit block to the move_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.

How do I block move_block completely? +

Set action: deny in the PolicyLayer policy for move_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.

What MCP server provides move_block? +

move_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.