Save research content to vector database for future retrieval.
AI agents use save_research_data to create or update resources in Research Assistant — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Research Assistant environment.
The tool creates or modifies records in a vector database, which is a Write operation. Severity is medium because while the data modification is reversible (given the delete capability), unauthorized saves could pollute the research database, consume storage, or enable later retrieval of sensitive information by other agents.
From the tool's definition Tool name 'save_research_data' and description 'Save research content to vector database' indicate creation/modification of data in persistent storage (ChromaDB vector database).
Attacks that exploit this kind of access
Save research content to vector database for future retrieval. It is categorised as a Write tool in the Research Assistant MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Research Assistant MCP server in PolicyLayer and add a rule for save_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.
save_research_data is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the save_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 save_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.
save_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.
save_research_data is one line of Research Assistant's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →