AI agents call remnote_search_by_tag 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 retrieves/queries notes by tag ID from a RemNote knowledge base, returning paginated results. It has no side effects—it does not create, modify, delete, or execute anything. This is a straightforward read operation typical of search/list functionality. Severity is low because misuse would only expose existing knowledge base content without enabling destructive actions or system compromise.
From the tool's definition Tool name 'search' and description 'Find notes' indicate data retrieval with 'cursor paging' for query results. No mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Find notes by exact tag Rem ID. Supports cursor paging through hasMore/nextCursor. Default resultMode=. 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_search_by_tag: 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_search_by_tag 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_search_by_tag 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_search_by_tag. 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_search_by_tag 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 →