AI agents use addJournalContent 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 or appends content to a journal in Logseq, which is reversible (can be edited or deleted later). It is a Write operation rather than Read (no query/retrieval), Execute (no code/script execution), Destructive (not irreversible), or Financial (no money movement).
From the tool's definition Tool name 'addJournalContent' indicates creation/modification of journal content. Sibling tools include 'addJournalBlock', 'addJournalEntry', and 'addNoteContent', which are explicitly Write operations on the Logseq knowledge graph.
Documented attack patterns abuse exactly the kind of access addJournalContent 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 addJournalContent:
{
"version": "1",
"default": "deny",
"tools": {
"addJournalContent": {
"limits": [
{
"counter": "addjournalcontent_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}addJournalContent 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.
addJournalContent. 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 addJournalContent: 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.
addJournalContent 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 addJournalContent 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 addJournalContent. 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.
addJournalContent 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.