engines
AI agents call engines to retrieve information from Free Search without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Without a description, confidence is reduced. However, the server context indicates search/fetch capabilities, and 'engines' most likely retrieves metadata about available search engines (a read operation) rather than performing searches or other actions. The tool name is consistent with a configuration or information query utility.
From the tool's definition Tool named 'engines' with empty description on a server described as enabling 'search the web, fetch pages, and read documents'. The name alone suggests listing or querying available search engines rather than modifying or executing actions.
Attacks that exploit this kind of access
engines. It is categorised as a Read tool in the Free Search MCP Server, which means it retrieves data without modifying state.
Register the Free Search MCP server in PolicyLayer and add a rule for engines: 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 Free Search. Nothing to install.
engines 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 engines 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 engines. 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.
engines is provided by the Free Search MCP server (sweetcornna/free-search-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →