Cancel a running or pending search by its ID.
AI agents call optimai_cancel_search to permanently remove resources in OptimAI Search MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling a search is irreversible — once cancelled, the in-progress operation cannot be resumed. While it doesn't delete stored data, it permanently terminates an ongoing process. This maps most closely to Destructive due to its irreversible nature. Severity is medium since the blast radius is limited to losing the results of a single search operation.
From the tool's definition Cancel a running or pending search by its ID
Documented attack patterns abuse exactly the kind of access optimai_cancel_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_cancel_search:
{
"version": "1",
"default": "deny",
"hide": [
"optimai_cancel_search"
]
}optimai_cancel_search disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Cancel a running or pending search by its ID. It is categorised as a Destructive tool in the OptimAI Search MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the OptimAI Search MCP server in PolicyLayer and add a rule for optimai_cancel_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_cancel_search is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the optimai_cancel_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_cancel_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_cancel_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.