optimai_list_searches

THE RISK

Low Risk

Why optimai_list_searches needs a policy

This tool retrieves historical search metadata (listing searches) without creating, modifying, deleting, or executing any operations. It is a pure read operation with minimal blast radius—an AI agent listing searches poses no direct harm beyond potential information disclosure of search history, which is already accessible to an authenticated user holding the API key.

From the tool's definition Tool name 'optimai_list_searches' and description 'List recent searches made with this API key' indicate a query/retrieval operation with no data modification or execution side effects.

Documented attack patterns abuse exactly the kind of access optimai_list_searches gives an agent:

POLICY

How to control optimai_list_searches

PolicyLayer is an MCP gateway — it sits between your AI agents and OptimAI Search MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for optimai_list_searches:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "optimai_list_searches": {}
  }
}

optimai_list_searches is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register OptimAI Search MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More OptimAI Search MCP tools

Destructive optimai_cancel_search Cancel a running or pending search by its ID. Execute optimai_start_search Start a Web3-focused AI search on the OptimAI decentralised network and return immediately Execute optimai_search Run a Web3-focused AI search on the OptimAI decentralised network. Read optimai_get_search Retrieve the current status and result of a previously created search by its ID.

All 5 OptimAI Search MCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about optimai_list_searches

What does the optimai_list_searches tool do? +

List recent searches made with this API key. It is categorised as a Read tool in the OptimAI Search MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on optimai_list_searches? +

Register the OptimAI Search MCP server in PolicyLayer and add a rule for optimai_list_searches: 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 OptimAI Search MCP. Nothing to install.

What risk level is optimai_list_searches? +

optimai_list_searches is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit optimai_list_searches? +

Yes. Add a rate_limit block to the optimai_list_searches 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.

How do I block optimai_list_searches completely? +

Set action: deny in the PolicyLayer policy for optimai_list_searches. 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.

What MCP server provides optimai_list_searches? +

optimai_list_searches is provided by the OptimAI Search MCP server (optimainetwork/optimai-search-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every OptimAI Search MCP tool call.

Start from OptimAI Search MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →