AI agents use remnote_insert_children to create or update resources in Remnote — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Remnote environment.
The tool creates new child nodes in a knowledge base hierarchy. This is a Write operation because it modifies the data structure reversibly - inserted children can be removed or edited. The severity is medium because misuse could clutter the knowledge base with unwanted entries, but the operation is reversible and doesn't permanently destroy data or cause financial harm.
From the tool's definition Tool name contains 'insert' and description states 'Insert new child Rems under a parent' - this creates new data structures.
Attacks that exploit this kind of access
Insert new child Rems under a parent at a deterministic position without replacing existing children. Use this for tag description nodes and hierarchy maintenance. It is categorised as a Write tool in the Remnote MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Remnote MCP server in PolicyLayer and add a rule for remnote_insert_children: 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 Remnote. Nothing to install.
remnote_insert_children 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 remnote_insert_children 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 remnote_insert_children. 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.
remnote_insert_children is provided by the Remnote MCP server (remnote-mcp-server). 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 →