search_notes
AI agents call search_notes to retrieve information from MCP Server Learning without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Search operations retrieve and query data without modifying, deleting, or executing external operations. Even in the context of an Obsidian vault, searching notes is a non-destructive read operation. Confidence is slightly reduced due to empty description, but the function name and server's educational purpose provide sufficient evidence for the Read category with low severity.
From the tool's definition Tool name 'search_notes' indicates a query/search operation. Server context describes educational tasks including 'Obsidian vault interaction,' suggesting this tool queries notes within a vault.
Attacks that exploit this kind of access
search_notes. It is categorised as a Read tool in the MCP Server Learning MCP Server, which means it retrieves data without modifying state.
Register the MCP Server Learning 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 MCP Server Learning. 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 MCP Server Learning MCP server (xstraven/mcp-server-learning). 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 →