Search local note titles and bodies.
AI agents call search_notes to retrieve information from Local Knowledge Desk without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
search_notes is a read-only operation that queries existing notes. It retrieves information based on search criteria but does not create, modify, delete, or execute external operations. This is the classic pattern of a Read category tool with minimal security risk.
From the tool's definition Tool performs 'Search local note titles and bodies' with no modification or deletion capability indicated. The description explicitly frames this as a search operation, which retrieves and queries data without side effects.
Attacks that exploit this kind of access
Search local note titles and bodies. It is categorised as a Read tool in the Local Knowledge Desk MCP Server, which means it retrieves data without modifying state.
Register the Local Knowledge Desk 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 Local Knowledge Desk. 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 Local Knowledge Desk MCP server (matiaslaukka/openai-mcp-project). 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 →