AI agents use addJournalBlock 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.
The tool name 'addJournalBlock' explicitly suggests creating or appending a block (note/content unit) to a journal within the Logseq knowledge graph. While the description is empty, the naming convention and context from sibling write tools (addJournalContent, addJournalEntry, addNoteContent) strongly indicate this modifies the knowledge base reversibly.
From the tool's definition Tool name 'addJournalBlock' indicates adding/creating content. Sibling tools include 'addJournalContent', 'addJournalEntry', and 'addNoteContent', which are clearly write operations. The tool pattern matches Write category operations.
Documented attack patterns abuse exactly the kind of access addJournalBlock 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 addJournalBlock:
{
"version": "1",
"default": "deny",
"tools": {
"addJournalBlock": {
"limits": [
{
"counter": "addjournalblock_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}addJournalBlock 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.
Free to start. No card required.
addJournalBlock. 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 addJournalBlock: 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.
addJournalBlock 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 addJournalBlock 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 addJournalBlock. 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.
addJournalBlock 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.