Save research content to vector database for future retrieval.
AI agents use save_research_data to create or update resources in Pocket Assistant MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pocket Assistant MCP Server environment.
This tool creates and stores new data entries in a persistent vector database (ChromaDB). While the operation is reversible (deletable via the sibling delete_research_topic tool), it modifies the database state.
From the tool's definition The tool 'saves' research content 'to vector database', describing a create/modify operation. The description explicitly states it stores data 'for future retrieval', confirming it creates new records rather than destroying or executing external operations.
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 Pocket Assistant MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pocket Assistant MCP Server 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 Pocket Assistant MCP Server. 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 Pocket Assistant MCP Server MCP server (vikashs/pocket_agent_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 →