Search the vector space using a sparse or dense vector.
AI agents call search to retrieve information from VecFS without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The search tool performs read-only retrieval of data from the vector storage. It queries the vector space to find matching memories or context but does not create, modify, delete, or execute any operations. The operation has no side effects and presents minimal risk of misuse by an AI agent.
From the tool's definition Tool name is 'search' and description states 'Search the vector space using a sparse or dense vector.' This is a query operation that retrieves data without modification.
Documented attack patterns abuse exactly the kind of access search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and VecFS, and nothing reaches the server without passing your rules. This is the rule we recommend for search:
{
"version": "1",
"default": "deny",
"tools": {
"search": {}
}
}search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search the vector space using a sparse or dense vector. It is categorised as a Read tool in the VecFS MCP Server, which means it retrieves data without modifying state.
Register the VecFS MCP server in PolicyLayer and add a rule for search: 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 VecFS. Nothing to install.
search 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 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. 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 is provided by the VecFS MCP server (wazzamo/vecfs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from VecFS, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 VecFS tools catalogued and risk-classified — across an index of 43,000+ MCP servers.