Search notes by title, content, tags, or workspace.
AI agents call search_notes to retrieve information from Streamline MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a read-only search operation on notes. It retrieves information based on search criteria but does not create, modify, delete, or execute any changes to the data or system. This falls squarely into the Read category with low severity, as misuse would only expose existing data rather than cause destructive or operational harm.
From the tool's definition Tool name is 'search_notes' and description states it 'Search notes by title, content, tags, or workspace.' This is a query operation with no side effects—it retrieves data without modifying, deleting, or executing actions.
Attacks that exploit this kind of access
Search notes by title, content, tags, or workspace. It is categorised as a Read tool in the Streamline MCP MCP Server, which means it retrieves data without modifying state.
Register the Streamline 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 Streamline MCP. 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 Streamline MCP server (rostehea/streamline-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 →