AI agents call search to retrieve information from ContextCore without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs information retrieval from indexed local files using hybrid search. It retrieves and queries data without modifying, deleting, or executing anything. The empty description lowers confidence slightly, but the server's explicit purpose (indexing and retrieving) and the read-only nature of sibling tools strongly indicate this is a query/search tool.
From the tool's definition Tool named 'search' on a server that 'indexes all your local files' and 'provides hybrid search (BM25+embeddings) to retrieve only relevant chunks'.
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 ContextCore, 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. It is categorised as a Read tool in the ContextCore MCP Server, which means it retrieves data without modifying state.
Register the ContextCore 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 ContextCore. 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 ContextCore MCP server (lucifer-ux/contextcore). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ContextCore, 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.
16 ContextCore tools catalogued and risk-classified — across an index of 43,000+ MCP servers.