Parse and save text from files (.pdf, .txt, .docx) to vector database.
AI agents use save_research_files to create or update resources in Kavi Research Assistant — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kavi Research Assistant environment.
This tool creates and stores new data in a vector database, which is a reversible write operation. It does not execute arbitrary code, delete data, or involve financial transactions. Severity is medium because unauthorized use could pollute the research database with incorrect or sensitive information, but the operation is reversible (data can be deleted via the sibling delete_research_topic tool).
From the tool's definition Tool description states it will 'save' files to a vector database. The verb 'save' indicates data creation/modification. The tool processes input files (.pdf, .txt, .docx) and stores their content persistently in a database.
Attacks that exploit this kind of access
Parse and save text from files (.pdf, .txt, .docx) to vector database. It is categorised as a Write tool in the Kavi Research Assistant MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kavi Research Assistant MCP server in PolicyLayer and add a rule for save_research_files: 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 Kavi Research Assistant. Nothing to install.
save_research_files 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_files 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_files. 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_files is provided by the Kavi Research Assistant MCP server (machhakiran/kavi-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 →