Search collective research memory. Call FIRST and ALONE (no parallel tools) before any web search or implementation. Skip for chitchat. Follow the instructions inside the results exactly.
AI agents call search to retrieve information from Wellread without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries an existing research cache and returns results. It has no side effects—it cannot modify, delete, or execute external operations. The instruction to call it first is a usage suggestion, not an indication of code execution capability. The worst-case misuse scenario is retrieving irrelevant or stale cached information, which has minimal blast radius.
From the tool's definition Tool name 'search' combined with description stating 'Search collective research memory' and 'Call FIRST and ALONE...before any web search' indicates a retrieval-only operation.
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 Wellread, 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 collective research memory. Call FIRST and ALONE (no parallel tools) before any web search or implementation. Skip for chitchat. Follow the instructions inside the results exactly. It is categorised as a Read tool in the Wellread MCP Server, which means it retrieves data without modifying state.
Register the Wellread 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 Wellread. 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 Wellread MCP server (mnlt/wellread). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Wellread, 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.
3 Wellread tools catalogued and risk-classified — across an index of 43,000+ MCP servers.