AI agents use addNoteContent 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 and server's documented write capabilities (addJournalBlock, addJournalContent, createPage) strongly suggest this performs reversible content creation or modification. It does not delete data (would be Destructive), execute arbitrary code (Execute), or handle financial transactions (Financial).
From the tool's definition Tool name 'addNoteContent' combined with server context showing write operations like 'addJournalBlock', 'addJournalContent', 'createPage' indicates content creation/modification. Description is empty, reducing confidence slightly.
Documented attack patterns abuse exactly the kind of access addNoteContent 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 addNoteContent:
{
"version": "1",
"default": "deny",
"tools": {
"addNoteContent": {
"limits": [
{
"counter": "addnotecontent_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}addNoteContent 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.
addNoteContent. 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 addNoteContent: 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.
addNoteContent 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 addNoteContent 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 addNoteContent. 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.
addNoteContent 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.