Search through saved research data using semantic similarity.
AI agents call search_research_data to retrieve information from Research Assistant without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a semantic search operation on existing research data stored in ChromaDB. Searching is a classic Read operation—it retrieves or queries data with no side effects. The tool does not create, modify, delete, or execute code. The low severity reflects that misuse would only expose existing data the agent should already have access to, not create new vulnerabilities or cause irreversible harm.
From the tool's definition Tool description states 'Search through saved research data using semantic similarity.' The verb 'search' and the read-only nature of semantic similarity querying indicate data retrieval without modification.
Attacks that exploit this kind of access
Search through saved research data using semantic similarity. It is categorised as a Read tool in the Research Assistant MCP Server, which means it retrieves data without modifying state.
Register the Research Assistant MCP server in PolicyLayer and add a rule for search_research_data: 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 Research Assistant. Nothing to install.
search_research_data 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_research_data 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_research_data. 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_research_data is provided by the Research Assistant MCP server (laxmimerit/research-assistant-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 →