Search notes using tag filtering, title search, and date filters (AND logic across all filters, OR within topics)
AI agents call find_notes_by_tags to retrieve information from MCP Note-Taking Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though find_notes_by_tags only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
Search notes using tag filtering, title search, and date filters (AND logic across all filters, OR within topics). It is categorised as a Read tool in the MCP Note-Taking Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Note-Taking Server MCP server in PolicyLayer and add a rule for find_notes_by_tags: 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 MCP Note-Taking Server. Nothing to install.
find_notes_by_tags 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 find_notes_by_tags 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 find_notes_by_tags. 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.
find_notes_by_tags is provided by the MCP Note-Taking Server MCP server (starrstack/mcp-notes). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.