Search notes using full-text search and return matching titles
AI agents call search_notes to retrieve information from Vimango MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries existing data (notes) and returns results without creating, modifying, deleting, or executing external operations. It is a classic Read operation with minimal risk even if misused, as search cannot harm data or cause unintended side effects beyond returning search results.
From the tool's definition Tool name is 'search_notes' and description explicitly states it performs 'full-text search and return matching titles' — a retrieval operation with no data modification, deletion, or side effects.
Attacks that exploit this kind of access
Search notes using full-text search and return matching titles. It is categorised as a Read tool in the Vimango MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Vimango MCP Server MCP server in PolicyLayer and add a rule for search_notes: 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 Vimango MCP Server. Nothing to install.
search_notes 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 search_notes 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 search_notes. 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.
search_notes is provided by the Vimango MCP Server MCP server (slzatz/vimango_mcp). 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 →