AI agents call search_vectara to retrieve information from Vectara MCP server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Search operations are inherently Read operations—they retrieve and query data without modifying, deleting, or executing arbitrary code. Even though the description is empty, the tool name and server purpose provide sufficient evidence of a retrieval function. The low severity reflects minimal blast radius: misuse would only over-retrieve or return unwanted information, not corrupt or delete data.
From the tool's definition Tool name 'search_vectara' indicates a search operation. The description is empty, which reduces confidence slightly, but the name and context (Vectara is a vector search/RAG platform) strongly suggest data retrieval without side effects.
Documented attack patterns abuse exactly the kind of access search_vectara gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Vectara MCP server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_vectara:
{
"version": "1",
"default": "deny",
"tools": {
"search_vectara": {}
}
}search_vectara 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_vectara. It is categorised as a Read tool in the Vectara MCP server MCP Server, which means it retrieves data without modifying state.
Register the Vectara MCP server MCP server in PolicyLayer and add a rule for search_vectara: 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 Vectara MCP server. Nothing to install.
search_vectara 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_vectara 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_vectara. 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_vectara is provided by the Vectara MCP server MCP server (vectara/vectara-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Vectara MCP server, 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.
6 Vectara MCP server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.