AI agents call free_general_search to retrieve information from Freesearch without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a search engine and retrieves results without modifying, executing code, or causing irreversible changes. Despite the empty description, the naming pattern and context strongly indicate a read-only search operation. Severity is low because search operations have minimal blast radius—worst case an agent performs many searches or exfiltrates data, but causes no system damage.
From the tool's definition Tool name 'free_general_search' and server description indicating 'search' functionality with SearXNG, a metasearch engine.
Documented attack patterns abuse exactly the kind of access free_general_search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Freesearch, and nothing reaches the server without passing your rules. This is the rule we recommend for free_general_search:
{
"version": "1",
"default": "deny",
"tools": {
"free_general_search": {}
}
}free_general_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.
free_general_search. It is categorised as a Read tool in the Freesearch MCP Server, which means it retrieves data without modifying state.
Register the Freesearch MCP server in PolicyLayer and add a rule for free_general_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 Freesearch. Nothing to install.
free_general_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 free_general_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 free_general_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.
free_general_search is provided by the Freesearch MCP server (wzj177/mcp-server-freesearch). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Freesearch, 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.
10 Freesearch tools catalogued and risk-classified — across an index of 43,000+ MCP servers.