Retrieve the current status and result of a previously created search by its ID.
AI agents call optimai_get_search to retrieve information from OptimAI Search MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries existing search results by ID and returns status/data without any side effects. It performs a pure read operation consistent with search result retrieval. No data is modified, deleted, executed, or accessed for financial purposes. The low severity reflects minimal blast radius—worst case is returning stale or unintended search results to an agent.
From the tool's definition Tool name and description indicate retrieval only: 'Retrieve the current status and result of a previously created search by its ID.' This is a query/fetch operation with no modification, deletion, or execution capability.
Documented attack patterns abuse exactly the kind of access optimai_get_search gives an agent:
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_get_search:
{
"version": "1",
"default": "deny",
"tools": {
"optimai_get_search": {}
}
}optimai_get_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.
Retrieve the current status and result of a previously created search by its ID. It is categorised as a Read tool in the OptimAI Search MCP MCP Server, which means it retrieves data without modifying state.
Register the OptimAI Search MCP server in PolicyLayer and add a rule for optimai_get_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 OptimAI Search MCP. Nothing to install.
optimai_get_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 optimai_get_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 optimai_get_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.
optimai_get_search 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.
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.
Free to start. No card required.
5 OptimAI Search MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.