List all active search sessions with their status.
AI agents call list_active_searches to retrieve information from OODA Computer Control without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about active search sessions. It performs no side effects, does not execute code or commands, does not modify data, and does not delete or move resources. It is a straightforward read operation that fits the 'Read' category for tools that query or retrieve data with no side effects.
From the tool's definition Tool name and description indicate it 'List[s] all active search sessions with their status' — a retrieval operation that queries existing state without modifying, executing commands, or deleting data.
Documented attack patterns abuse exactly the kind of access list_active_searches gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OODA Computer Control, and nothing reaches the server without passing your rules. This is the rule we recommend for list_active_searches:
{
"version": "1",
"default": "deny",
"tools": {
"list_active_searches": {}
}
}list_active_searches 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.
List all active search sessions with their status. It is categorised as a Read tool in the OODA Computer Control MCP Server, which means it retrieves data without modifying state.
Register the OODA Computer Control MCP server in PolicyLayer and add a rule for list_active_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 OODA Computer Control. Nothing to install.
list_active_searches 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 list_active_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.
Set action: deny in the PolicyLayer policy for list_active_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.
list_active_searches is provided by the OODA Computer Control MCP server (mnehmos/mnehmos.ooda.mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OODA Computer Control, 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.
99 OODA Computer Control tools catalogued and risk-classified — across an index of 43,000+ MCP servers.