AI agents call remnote_list_children to retrieve information from Remnote without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data retrieval only—listing child elements in a knowledge base hierarchy. It has no side effects, does not modify data, and does not execute external operations. It is purely informational, making it a Read category tool with low severity since misuse would only expose or enumerate existing data without causing harm.
From the tool's definition Tool name 'remnote_list_children' and description 'List direct child Rems under a parent without rendering a subtree' indicate a query operation that retrieves hierarchical data without modification.
Attacks that exploit this kind of access
List direct child Rems under a parent without rendering a subtree. Use for cheap hierarchy traversal; page with nextCursor when hasMore is true. It is categorised as a Read tool in the Remnote MCP Server, which means it retrieves data without modifying state.
Register the Remnote MCP server in PolicyLayer and add a rule for remnote_list_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_list_children is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the remnote_list_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_list_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_list_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 →