Search the web using MiniMax. Returns search results with titles, snippets, and URLs. Use this when you need up-to-date information, facts, news, or references from the internet.
AI agents call mmx_search to retrieve information from Mmx without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
mmx_search is a query tool that retrieves and displays information without side effects. It performs a search operation and returns data (titles, snippets, URLs) without creating, modifying, deleting, or executing any operations. This is a straightforward Read category tool with minimal security risk.
From the tool's definition Tool description states it 'Returns search results with titles, snippets, and URLs' and is used to retrieve 'up-to-date information, facts, news, or references from the internet.' No modification, deletion, or execution capabilities are mentioned.
Documented attack patterns abuse exactly the kind of access mmx_search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mmx, and nothing reaches the server without passing your rules. This is the rule we recommend for mmx_search:
{
"version": "1",
"default": "deny",
"tools": {
"mmx_search": {}
}
}mmx_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 the web using MiniMax. Returns search results with titles, snippets, and URLs. Use this when you need up-to-date information, facts, news, or references from the internet. It is categorised as a Read tool in the Mmx MCP Server, which means it retrieves data without modifying state.
Register the Mmx MCP server in PolicyLayer and add a rule for mmx_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 Mmx. Nothing to install.
mmx_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 mmx_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 mmx_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.
mmx_search is provided by the Mmx MCP server (zth0828/mmx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Mmx tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
8 Mmx tools catalogued and risk-classified — across an index of 42,500+ MCP servers.